Unfortunately this greatly reduces the utility of CenarioVR, because it makes native (to my company) tracking of the courses impossible.
I have not dug into your products’ features in detail–can the CenarioVr server act as a SCORM proxy, so we could launch a course from our own LMS but open it in the app? That’s yet a third variation of each course we would have to build: iDevices (can’t use high resolution video), headsets, and everything else. It would also add a lot of complexity to the LMS setup at our end–we’d have to assign a course with three possible branches to each student, then have them pick the appropriate one depending on which device they are using. For Lectora courses, you also lose the “resume where you left off” capability because, of course, there would be two separate Lectora courses, and one “pure” CVR course that doesn’t even relate to Lectora for headsets. You could not leave off in the Oculus Go and resume on your iPad or ThinkPad.
From what you said in the video you kindly directed me to, Lectora courses incorporate the HTML5 export of the scenario, which is not (from what you say in the message above) supported by headsets. Have you considered creating a new transport type (tvcvr://URI-of-secnario?) to launch the app, if available? You could also build the ability to detect that it is running on headsets directly into Lectora 19–courses already detect other platforms (e. g. iPhone vs. PC). This would be similar to the way some web conferencing companies create their own transport type to launch their apps, both on PCs and mobile devices.