threads.net is the domain. You can get a head start and block any IP addresses associated with it using the firewall of your choice.

Oh, more meetings will fix it! /s

DD might be using something like that. I have heard they block TOR as well. I have used a VPN with ports 80 and 443 on their WiFi years ago.

Deep packet inspection is unlikely the culprit in my experience. SSH and SFTP use port 22 by default which is probably blocked. I log in to my work VPN through common ports 80 and 443 on public WiFi.

You could also have your back end pull from a git repo every minute. A cron job could check a GitLab repo for changes and update the site if any changes are found.

That is a networking issue which is not specific to Hugo. You need to solve this as most of the suggestions also involve SSH.

One way is to use a VPN like openvpn or wireguard that can use a common port like 80 or 443.

What do you find limited about Hugo?

I would recommend making a full git repository and at least adding a license header so that others can expand upon it. Maintaining a useful gist is cumbersome as issues tend to be ignored comments.