After talking with LordCrc tonight in IRC I think I have a even more well defined model of how to move forward with this.
Creating a new dir in the lux source main branch called luxstudio which will function as a prototype. It will be another version of the luxrender UI using Qt. One main goal is to not effect the core lux lib which I think this model satisfies.
Luxstudio will be able to import mesh files, wave front objects and hopefully luxrender meshes and display them using initially opengl but with a render engine abstracted beyond a specific platform.
It will be able to export luxrender scenes but have its own luxstudio file format based on xml right now and storing the scene as a tree structure. The argument being that the lux scene format is not really a transportable format. Part of the idea is that exporters can read the luxstudio file to resync the positions of objects, lights and the camera.
The value of this is it will allow the luxstudio prototype to be developed without waiting for api changes but when api changes are implemented they can be incorporated easily. Also it will support the development of a mesh handling sub-section in the GUI which can evolve into a separate mesh handling lib.
So the introduction of luxstudio will have very little if any impact on the core but at the same time lay the groundwork for expansion of the api when time allows and also support experimentation with different compartmentalization models.