Eventhub and bootorder?

So I just read and listened to Adams’ Youtube session on Eventhubs (https://www.youtube.com/watch?v=BK7XvIMnVss). ANd as I understand it, it works like this:

On the PSU server, create an Eventhub (for example MyCoolHub).
On the client, install the Powershell Universal Agent, pointing (via the JSON config file) towards the PSU server

After the above is setup, commands may be send to MyCoolHub and commands are then sent out to the clients connected to that Eventhub.

Hopefully I got the above right. Now for my question:

WHen we patch servers ((PSU server and the Eventhub clients, do we need to consider boot order, ie bot the POSU server first then the clients, or can they re-establish the conenction even if the PSU server is not available when the clients are booting (or for that matter, if the PSU server reboots, can the clients re-connect?)

The way I’m planning / thinking of this feature is software management. Ie msi-packages are put in a location that the clients can reach and whenever there is a new version available in that place, we send out msiexec xxxx /quiet to the clients.

Has anyone done this and is happy with the results? Why / why not?