@DustinB3403 yes. Exactly. Installing a node= put the virt engine on the node. Like installing xcp or so.
Hyperconverged means each or some nodes exposes a gluster brick to create shared storage.
Than on that storage (couple of years ago exposed via iscsi, dont know anything about current setup) you create a special VM which is the orchestrator (XO)

@DustinB3403 it is like putting XO in a VM inside xcp. The major difference here is the gluster layer.

Which a lot of people do all of the time. Could you install it as bare metal on a separate host, absolutely. Should you, meh depends on what you need.

You can do the same with ovirt. The gluster layer is for redundancy. In a First lab you can directly put ovirt into a single Vm into a single node.

Just mind you have to put the orchestrator in a special state before node reboot. I didn't figured this out at the time and after the first reboot everything gone nuts.
I Abandoned the idea in favor of virtmanager + vanilla kvm.

Besides these two there is the localhost-oriented libvirt with virt-manager, cockpit and boxes, and kubernetes oriented kubevirt.

So if you're looking for a vCenter cluster replacement, RHV is what you should be looking at (or if you prefer the less stable opensource version - oVirt). If you want to build something larger, at the scale of AWS, you need Openstack. For local stuff, e.g. virtualbox - virt-manager, boxes, and eventually cockpit will do the job, and if you want to run a VM in a k8s pod - kubevirt is for you.