1. If you aren’t seeding (no one is downloading the torrent), then your bandwidth should not be used (besides a miniscule amount). So it shouldn’t waste your bandwidth. Is your concern about wasting bandwidth more about seeding a torrent when there are other seeders available? So you want to prioritize torrents that have zero other seeders?

2. It looks like this tool Jackett (I’ve never used it before; just found it in a search) can be configured to allow your system to query trackers for torrents and return the number of seeders and leechers. But a lot of assembly would be required. And the freshness of results would depend on how often trackers update their stats - definitely not real-time.

For a torrent application that can do what Jackett does in real-time by connecting directly to the torrent and prioritizing bandwidth to torrents that have leechers and no other seeders, I’ll leave that to others in the community more familiar with the topic.

This site worked for me: https://yt6d.com/

I requested all versions from 720p to 2160p, so they might be cached and get around whatever blocks you were encountering.

Can I be added to the recall? 🥹

https://youtu.be/3m5qxZm_JqM

If two files have the same hash, you may receive the file you request by hash, or you may receive a different, possibly malicious file.

https://en.m.wikipedia.org/wiki/Collision_attack

Strong cryptographic hashes are resistant to such attacks, but md5 is relatively weak.