Happy to help... as you read there, the Asus-Merlin FW built-in killswitch has its limits. In certain cases it won't work if your vpn connection stops. This is why, in the other post,
@eibgrad suggested creating your own killswitch to get around these limitations. He was successful in building one (
here). I had run with his idea, and built KILLMON that takes it a step further, and gives you some other options on protecting your devices in the event your vpn connection goes down,
available here.
I had also been dealing with my VPN connection going down all the time, and not having a good way to monitor it, or have it automatically reconnect. I built VPNMON-R2 for that purpose, and that has kept our VPN connection running 24x7 for years now. It really does work well for my purposes, and like the fact that I can randomly pick from 2000+ endpoints to appear from when it reconnects after a failure, or from a scheduled reset. If you haven't already played with that, you can get that
here
The VPN Director is simply a tool to allow you to select which devices need to route over which VPN connection. In the guide I wrote, i recommended that you build one configuration for each of your VPN connections in order to force your local network traffic out over it, incase VPNMON-R2 switches from VPN slot #1 to #3, for instance. That way you're always guaranteed that your network traffic is being forced out through a VPN connection, if there is one present. It works surprisingly well.
The VPN Director is not going to automatically reconnect your VPN connection, if that is what you were asking. You will need a tool, like VPNMON-R2, to perform that reconnection task.
The killswitch setting you are describing acts independent of VPN Director. You can have rules on or off, it doesn't affect whether or not you want to use the built-in killswitch.
Hope that helps!