Very neat indeed! Similar tools have done a lot to make TeX more accessible, so it makes sense that this also benefits lilypond.

I've started work on a project of my own that will do online rendering of lilypond (rather different design objectives from yours, though). I've been worrying a bit about resource consumption of frequent renders, and your application is occupying a rather extreme point there. Do you have any data about this already?