I'm trying to figure out bittorrent options in i2p and I'm a bit stuck.

I planned on setting up a container with a bittorrent client on my home media server and letting it communicate through the i2pd relay I set up elsewhere on my network. But I see some clients use SAM to talk to the relay and others use I2CP to talk to the relay. What's the difference? Is there any advantage in choosing one over the other?

I'm also a little stumped on clients. I don't like the idea of the relay being anything but a relay so I use i2pd instead of i2p or i2p+. I also hate Java so I steer clear of it whenever I can. BiglyBT seems to be the gold standard of I2P torrenting because it supports every feature and function within I2P. But it's java based and doesn't seem to have a headless UI. qBittorrent is a relative newcomer to I2P torrenting but seems to have some missing features like DHT. Is DHT all that important? It can run headless and doesn't need java. I2Psnark/I2Psnark+ are built to run built within the router and can be convenient, but I dislike the idea of the router accessing local network resources directly and would prefer if the resources on my network offered them through the relay rather than the relay directly fetching them.

Ultimately, the idea will be I tell my media server "Go get the thing, then just keep sharing it with others until one of us dies" and the media server will speak to the darkweb through a physically separate relay on my network. I'm just not sure of the best way to do this.