You can do it, but I am thinking the implementation is wrong. On the PVS image, you need to do a Cloud Robot Install set to a reboot of 1. Then put a request.cfg file in to download a SuperPackage with probes and configs or use MCS to redeploy the probes and configs.
Each robot needs a unique id, once a robot has checked into a hub, now that is stored in niscache and the DB. You can't do that to an image. I suspect there are issues with the inventory and QOS linkage for those devices now.
Been there done that.
Note they need to be careful when they open that image for updates, they need to reinstall the Robot or make a backup copy of the Nimsoft folders after install then when the "seal" the image they delete the Nimsoft folder and copy the backup of the Cloud Robot install back in.