But, as you said yourself, if Hubs want that sort of info/control, they can do it now via Octoprint or other hardware/software solutions.
How would 3DHubs talk to your local printer? It’d have to be over the web which introduces a massive single point of failure in the comms. All you need is a momentary failure of net connectivity and your customer print fails. You’d really need it to act like a remote interface for a local print server so a comms failure wouldn’t affect the actual print and that’s… er… Octoprint, it already exists.
Sorry if I sound negative, but given there are already tools out there to do what you’re thinking of, which a lot of hubs are already using, and the huge undertaking it would be in terms of development and support, I’m not sure it’s practical or really necessary/desirable.