That seems like a case where a reverse proxy like NGINX[1] would be useful. The configuration would basically be:
User->HTTPS over public internet->NGINX->HTTP on your private network->Custom appliances
The most vulnerable link (the public internet part) would still be encrypted, and browsers won't show the scary warnings. The HTTP connection would be confined to your private network, where MITM is less of a concern.
You can use one NGINX instance to reverse proxy multiple different appliances, so the maintenance overhead wouldn't be that high.
[1] https://docs.nginx.com/nginx/admin-guide/web-server/reverse-...