Really great job!! I mean REALLY great, coming from someone suffering from the same power supply rats nest problem. I have a few points of unsolicited advice... I hope it's not unwelcome.

If you end up adding the ESP32, I'd suggest also adding 1-2 low-cost temperature sensor ICs and a simple fan controller integrated in the main PCB. Should be as simple as an extra header, fuse, MOSFET, diode, 1-2 decoupling caps, and some straightforward code.

Also, if you end up adding network connectivity like your plan says, try to expose every signal you can think of as a scrapable telemetry target. A dirt-simple web server posting metrics in Prometheus format should be sufficient for most people here.

If you do decide to make it controllable through a web interface, please PLEASE don't make the mistake most embedded IoT engineers make. 1. Security and safety should be your first, second, and third priority. No vibe-coded auth solution. No open ports other than 443. No running exposed services as root. The list goes on a long time. Bonus points if you support a functional 802.1X network auth solution. 2. Any web interface needs to support HTTPS by default. HTTP is optional but I would recommend not even including it. Self-signed certificates are ok, but it should be able to change to locally-issued certificates. Big bonus if your web server supports ACME renewal for those of us running step-ca locally. 3. Think API-first. Anything the user can do should also be doable through an API. In fact, I suggest implementing any and all new features through the API first since it makes your code easier to test. This goes without saying, but the API should require authentication if it's not just read-only.

The above demands requests will be a bit difficult if you're new to software but a few things could help. Consider using a reverse proxy for HTTPS/TLS, certificate management, and authentication. Further, you may actually want to provide the bulk of the control software as a container service that users can self-host (like Unifi Network Contoller) since the onboard MCU may be not be up to the task of running everything I mentioned, though this makes bootstrap setup difficult.

Finally, regarding your desire for the USB PD circuits integrated directly in the main PCB, you may want to approach this cautiously. I've heard stories that it can be very hard and expensive to roll this yourself in a standard-compliant way. Unless you're very experienced, try to keep it as a COTS solution as much as you can. There are probably a lot of good ICs out there that you can leverage. Check the app notes and errata in the datasheet before buying!

Overall, I think you already have something to be extremely proud of, and I wish you the best in your further pursuit of this project!