IMO, you are seeing the VPN service not in its intended way.
VPN is not supposed to provide you with publicly accessible, reliably static IP, it supposed to hides your traffic, obfuscate it along with the rest of their clients traffic so no one in the world knows which traffic belongs to who.
I would suggest that you do not use a static IP for torrenting, having a static IP that always associated to you all the time used for ‘torrenting’ would makes them put a crosshair on you, pretty fast and very confidently, and ultimately, viciously (because they now have a ground).
So what you can do ? I have a following example, this can be applicable both in PC and server environment. You have your static IP, not from the VPN. You also have your VPN. Attach your IP to your machine/VPS/VM, have it also run the VPN. Most known VPN protocols generate a virtual network interface for its ‘connection’. You can set your torrent client to bind to this interface, thus making it only send/receive data strictly through your VPN. Your VPN traffic of course will course along your static IP traffic, but worry not, since it is perfectly “tunnelled” through the VPN’s server first before actually ‘hits’ the internet.
Now, what’s the VPN to use ? if you are actually cares about torrenting, the least you can do if possible is ‘sharing’ back (well, this is where the VPN will always required). This is where you’ll need Port Forwarding.
Long story short, VPN with Port Forwarding feature allows you to seed but anonymously, so they won’t point their crosshair on you even more viciously (because now you are actively contributing in the ‘torrenting’ scene)
Azire, Proton and (probably) AirVPN are fews that i knows that have port forwarding.
Mullvad while great in speed, choices, and availability, and speed, they just sunsets their Port Forwarding feature.
You can download torrent just fine with any “privacy” oriented VPN, but not all allows you to seed.