I think it would work if the interface was installed with KiCad, as the current SWIG based one is. Otherwise trying to work out which version a user needs to download and install will make it unusable except by expert users.
I think managing available plugins is a separate issue. Handling dynamic content is something KiCad has just not got to grips with yet. We've had various piecemeal methods (currently 3 different methods I think), and the github method for footprints as default is being rolled back for next release.
Arduino IDE faced a similar problem with a plethora of third parties libraries and API cores, which were a mess for the user, similar to how KiCad works now. Arduino came up with a simple, lightweight method which is still quite powerful.
Described at https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.6.x-package_index.json-format-specification
Hmm, that could be a problem. Curated content is nice, but finding curators is difficult. I would prefer a scheme that can operate with minimal input in the first instance. If a plugin is faulty, contact the author or uninstall it. The Arduino plugin framework works like that, Arduino maintain a list of third party content, but they don't vet or approve content.