Firstly, you may be able to do everything, all of it through SSH config files. This is especially true if you're just SSHing to the end machines. See the SSH multihop config. With appropriately established SSH configs you could just assign destination names and type ssh servera or ssh serverb, instead of having to set up an SSH tunnel and then type tsocks ssh servera.
Tsocks really can't differentiate what you want. One approach would be to set up two config files and issue commands to swap configs for each network
eg:
$ chmod +x /usr/local/bin/tsocksa.sh
$ cat /usr/local/bin/tsocksa.sh
#!/bin/bash
#
#Swaps for Network A
#See /etc/tsocs.conf.main and /etc/tsocks.conf.dest_a
#
sudo cat /etc/tsocks.conf{.main,.dest_a} > /etc/tsocks.conf
and
$ chmod +x /usr/local/bin/tsockss.sh
$ cat /usr/local/bin/tsockss.sh
#!/bin/bash
#
#Swaps for Network S
#See /etc/tsocks.conf.main and /etc/tsocks.conf.dest_s
#
sudo cat /etc/tsocks.conf{.main,.dest_s} > /etc/tsocks.conf
Now you would put your network-swap specific commands into /etc/tsocks.conf.dest_n and put your generic networks into /etc/tsocks.conf.master
You could also use Bash aliases for the same commands, or further simplify the Bash script into a function you can source in your bashrc.