It’s great to have something up and running in minutes to only redo it slightly differently.
If you are considering two proxmox hosts ensure the second one added to the cluster is an empty proxmox host, and the proxmox cluster from the first box will assign unique id’s to all containers on any host.
By default, the HA mode insists that all nodes are up or others won't come up, making this tweak (it may be contained in the OP scripts, I don't recall) allows you to retain many of the benefits of having Proxmox machines "connected", without requiring you treat them like a HA cluster.
In my case, I have a node I shutdown when it's not used, I use it for specific occasional tasks, and then I have nodes I want up all of the time.
With the non-HA tweaks, you can still do things like centrally manage, migrate VMs and containers between nodes etc, without the limitations of it wanting them all up and available all of the time.
I don't really use the HA features of proxmox that often, mostly just for migrating vms across hosts. But I had been thinking of re-installing some of my remote servers with proxmox and hooking them up to the same cluster so that I could potentially shut off all of the servers in my basement and run everything from a remote location, then migrate the vms back later.
There's also the issue of quorum of it's only a 2-node cluster, though I've personally not had any issues with it, despite repeatedly restarting the different nodes.
I see no reason why you couldn't do this to allow you to move your VMs from home to elsewhere and back again as you just mentioned.
I thought quorum feature of proxmox was also latency sensitive, but this is the only thing I found:
https://pve.proxmox.com/wiki/Cluster_Manager#pvecm_cluster_n...
Maybe this doesn't matter if not using HA? I'll read more about it and maybe test it out
Just my experience though, YMMV.