People keep saying "protect trans students" but what does that functionally mean? They get higher care/priority over other students getting bullied? Can you explain what it means exactly? It all seems very vague and needlessly divisive if you ask me.
As long as you're certain your wireguard server works from other networks.. You could use nginx as a proxy to have your server accept incoming traffic from UDP port 53 (DNS)... But, be careful!
I would strongly suggest you whitelist the restrictive network for use on UDP port 53. Is the WAN IP static on the restrictive network? Do you know the size of the WAN subnet? I'd try a quick test over UDP port 53 using nginx, then close it up. If it works, create your firewall rule to whitelist only the restrictive network and Bob's your aunt.
PS: If the restrictive network uses DPI (deep packet inspection) to verify they are real DNS queries on UDP 53, you can try putting DNSmuggle behind nginx. Do not have anything listen on localhost:53 as that may interfere with your local DNS at the server side. I don't know how well this will perform, but I'm assuming not amazing. DNSmuggle supports encrypted DNS, which should prevent the network(s) from hijacking your requests.
Labels and file locations can't be changed on the native transmission webui from what I could tell.. RPC supports it, but no luck on the webui... But I did come across this! https://flood.js.org
Flood is an alternative webui compatible with rtorrent. It says it's "touch ready". I have not tried it, but it might be exactly what you're after.
Use transdroid or transdrone. Make sure you set up http RPC on the server and enter your RPC path when selecting "rtorrent" while adding a custom server.
See this tutorial: https://bytesized-hosting.com/pages/transdroid
The SCGI path will be /rutorrent/plugins/httprpc/action.php
You may need a plugin or config change depending on what installer/package you used on your system.
rutorrent doesn't seem very intuitive, which is why I use transmission-daemon on my seedbox. In my experience transmission tends to just work.
Surprised he didn't lead with the "let's stop racism" routine. I admire his candor in his call for censorship in Canadian media.
PiKVM is a collection of tools rolled into a distro to make keyboard/mouse input and attaching an emulated install media (virtual USB disk using ISO files) easily possible through a VNC-based web application. The idea is you can just build your own using the same software on different hardware, but it's aimed at using a raspberry pi for low power consumption, portability, and it has specific hardware compatibility with a HAT/addon board. The software can also make "reverse connections" through a remote NAT for support purposes, and you'd just port forward on your end. There are a lot of well thought out features in PiKVM (hardware) that make it much more convenient than building your own solution. You could install PiKVM on a different system than a Pi and try to make it work with your configuration.. You'd probably lose things like simulated power button press and virtual USB storage support. You might consider alternatives like PXE/netboot and wake-on-lan for those, but that might not always work for you.
(YMMV, I have not tried running PiKVM on an x86 cpu)
I can't offer advice, but I do support this idea! Consolidate the sports!