The only real constraint here is VPN port forwarding. You would need a VPN provider that supports that in order to hit DHT swarms. So, just make sure the provider has that.
As for kill switching, run the VPN and torrent client through docker. There is probably already a docker image out there that does that depending on what provider you go with. Essentially what you'd be doing is sandboxing your torrent client and then only passing in the VPN interface via docker network to that client. If the VPN tunnel goes down there is no other egress point off the network segment and zero chance for traffic using a different interface.
Pretty sure that is just a discrepancy between when a site has last checked client announcements from the tracker and when what the tracker currently shows. As of 2025, TPB for example links to 3.2 million torrents. Assuming client announcements were set to an average 1hr interval, that would require TPB to make 76.8 million checks every day for announcement updates.
So, I could see sites not maintaining accurate seeder/leecher data.