If you don’t exceed a single deployment, it’s fine.

If however in the future, you want to add additional services to your host, let’s say an alerting or status system, it’s a lot easier to declare everything in a single place and then attach a reverse proxy to manage networking multiple services on one host.

As I use docker for most of my deploys (as you should for websites exposed to the Internet anyway), I can wholeheartedly recommend traefik for this. Basically it has the functionality of nginx, but supports easy Let’s Encrypt certificates.

To some degree you could, but you’d either rely on Tier1 transits to access the entire internet (costly), or you’d use IXPs (keeping your traffic local to other IX participants).

This doesn’t account for how’d you’d actually go into purchasing a port for your residential home, which would probably entail laying your own fiber to a data center nearby.