The IP of the cloud VM is never exposed. Only the VPN's.
If you're worried about dropbox type surveillance, you store the data in an encrypted drive.
2) use a VPN that has a reputation for not keeping logs and turning people over.
A cloud VM does seem overkill.
1) Looks like it also runs a headless Transmission client, so you could use it as a seedbox
2) It can be tricky to configure VPNs correctly so that if the VPN connection goes down, your traffic doesn't spill over onto the clearnet. If this Docker image ensures that aspect works correctly then that's helpful.
3) It's a little complicated to setup a VPN connection on a personal computer just for BitTorrent use, without having other traffic (e.g. browsing) spill over onto the VPN. Setting this all up on a segregated remote box and connecting to the headless Transmission client mitigates that.