You've basically got it. A reverse proxy listens on one port (usually 80/443) and looks at which name the request came for, like jellyfin.home.lan or notes.home.lan. Then it forwards the request to the right service on whatever port that service actually uses. Same box, one front door.
For day to day, you get:
- Names instead of IP:port. This part needs local DNS too. Your router or Pi-hole has to point those names at the proxy, and people forget that step.
- HTTPS in one place. The proxy holds the certificate, so your apps don't each need their own. This matters more than it sounds. Some apps, Vaultwarden for one, won't work properly over plain HTTP unless you're on localhost.
- A single spot for access rules, headers and logs.
It isn't only for exposing things to the internet. LAN-only setups use it for the names and HTTPS.
Would I skip it as a beginner? Mostly yes. With a couple of services, bookmarks with ports are fine, and you'll learn more by getting the services stable first. I'd add it the day one app demands HTTPS or you get tired of remembering ports. Nginx Proxy Manager has a GUI and is the gentler start. Traefik and Caddy are config-driven, which I prefer later, but they're more to learn at once.
What are you running on the mini PC? That changes whether HTTPS is a want or a need.