Yes, when PS has built-in robust authentication you could conceivably drop cloudflared and go back to poking holes (port forwarding) in your firewall and some sort of dynamic DNS setup pointing to your home IP address. I’d probably still want SSL support to even consider doing this, but that could be achieved with a local caddy/traefik reverse proxy setup.
But authentication is only one of the use cases for the cloudflared tunnel so for me at least, it’s here to stay as long as it stays free.
If PS wanted to make self-hosting truly non-geek friendly, it would have to implement some sort of cloud offering that would essentially do what cloudflared does. Plex, Home Assistant (and quite a few others) all offer something like that as part of their product - usually for a small additional fee.
Their implementation details vary, Plex for example opens a port with UPnP (I am not a fan) and then forces everyone to login through their cloud offering, which then redirects the user to your public IP address (so they don’t actually proxy the content).
Home Assistant will proxy everything through a randomly generated URL on their domain (not a fan of that either). Read more here: Remote UI
I would suggest either approach are well beyond the scope of the previously mentioned multi-user feature request. It could be submitted as its own feature request, but I am not going to do that because I personally don’t care for it 