You didn’t just add everything from that PCC article, did you? I hoped it was clear that I meant it as a learning material, to understand what you need to do about connection and route marking. In other words, I was lazy to write full explanation myself (Van9018 did it few posts later) and that article has nice explanation of what’s happening.
If you don’t want load balancing, remove the two rules with per-connection-classifier option. For the rest, this:
add action=mark-connection chain=output connection-mark=swift_conn new-connection-mark=to_swift passthrough=yes
should be:
add action=mark-routing chain=output connection-mark=swift_conn new-routing-mark=to-swift passthrough=yes
And you also need to add:
/ip route
add check-gateway=ping distance=1 gateway=192.168.1.1
And to avoid all possibilities that these connection marks could conflict with your torrent connection marks, you should add connection-mark=no-mark option to your torrent marking rules (those with action=mark-connection).
And about remote access, you have to open some port (VPN should be better than bare WinBox), otherwise you won’t be able to connect.