I've been pondering, as one like myself would ponder, about exporting the data-retrieval functions of LibRockConfig-1.0 and then having third-party libraries use these same functions to create their own configuration menus. This could be used for a dropdown system (a la Dewdrop) or a slash command system (a la AceConsole) or whatever. The major advantage to doing this is that it would eliminate the issue that Waterfall/AceConsole/Dewdrop had before where each had to write their own data retrieval functions and none would be consistent. The only problem that remains (that I honestly don't know how to solve) is that then things wouldn't necessarily be consistent from the user's point of view.
To be honest, as long as the library code that handled all this was consistent and complete i don't think it would matter if the manner in which things were displayed was inconsistent. Most users would not mix and match the different display systems, they would just use the one they prefer and ignore the rest. The problem only arises if they have to use multiple display systems to be able to handle everything because certain things are only available in each one.