VRSpaceUI is a singleton by design, so it can be used with only one scene at the moment.
Another VRSpaceUI can be created with another scene as an argument, but VRSPACEUI global is used all over the place.
This can be refactored so that few methods that require the scene need to take scene as an argument. And/or appropriate UI can be fetched with a method that takes scene argument.
It is not yet clear what this would be used for, a specific use case would make it easier.