It sounds like you have a fairly simple use case. Assuming that you are only operating as a forwarder (i.e. you do not have a large set of zone data or complicated configuration to reload) you might as well just have something which just changes the configuration file and then causes named to reload it using "rndc reconfig"
What I might do to make this a little cleaner would be to use the "include" directive in your named.conf, e.g.
# {stuff that you do all the time}
blah
blah
blah
# ISP specific forwarding section
include "ISP-forwarder-config.conf";
# {other stuff}
and then have "ISP-forwarder-config.conf" be a symlink that you can switch between target files for "ISP-1.conf" and "ISP-2.conf". (choose your own names, but the idea is that if you are only switching the symlink and not messing with your master named.conf file all the time there's much less chance of suffering some mishap that messes up your config.
To change forwarders, then, all you would need to do is change the target of the symlink and do an "rndc reconfig"