I can answer this one, but mainly only in reference to the other popular solutions:

• nginx. Solid, reliable, uncomplicated, but. Reverse proxy semantics have a weird dependency on manually setting up a dns resolver (why??) and you have to restart the instance if your upstream gets replaced.
• traefik. I am literally a cloud software engineer, I’ve been doing Linux networking since 1994 and I’ve made 3 separate attempts to configure traefik to work according to its promises. It has never worked correctly. Traefik’s main selling point to me is its automatic docker proxying via labels, but this doesn’t even help you if you also have multiple VMs. Basically a non-starter due to poor docs and complexity.
• caddy. Solid, reliable, uncomplicated. It will do acme cert provisioning out of the box for you if you want (I don’t use that feature because I have a wildcard cert, but it seems nice). Also doesn’t suffer from the problems I’ve listed above.

Proxmox VE is a packaging of Linux as an operating system. It is a distribution. Straight from the wikipedia page:

It is a Debian-based Linux distribution with a modified Ubuntu LTS kernel[7] and allows deployment and management of virtual machines and containers.[8][9]

Cool way to respond to a comment btw:

Am I taking crazy pills?

The VMs I’m running in Proxmox are also Linux, but that’s less interesting to me.

I installed Slackware in 1994 or so. Floppy. Disks.

Fast forward almost 30 years and I’m still trying new (to me) distros. Proxmox VE this time.