A rather simple solution would be to develop a "toolkit" of sorts... where the theme-editor relies on static modules, (ie, always and forever uses vtray for the systray, rainmeter for sys monitoring, jdesktop for the desktop, etc.) Themes created with this theme maker would always use the same module versions. Being restricted to only certain modules (and versions) would ensure that the theme maker would always work (disregarding any major changes to the Litestep build), and create useable themes. Of course the intention is not a replacement for text editing of themes, but as an alternative route for those without the comfortability in intricate editing.

Actually, now that I think of it, you could possibly make a "theme" that itself acted as such a Theme-Editor... lots o'scripting I'm sure, but it certainly seems possible...

Please, feel free to add your thoughts.