I think you are going out of your way to shoot down the idea and in doing so have not grasped what I am actually proposing.
It is not relevant whether an emulator presents its configuration options in drop down menus, via plugins, etc. There are only two ways that it can store them - in a flat file (ini, xml, etc.) or in the registry. Both of these are very easy to manipulate programatically.
I agree. All I am proposing is that a user can modify their controller config for various emulators from a single location. A simple GUI might involve selecting Snes9x from a list and being shown a SNES controller with a text box by each button. The user then clicks a text box and presses the key they want to use. Repeat for each button - exactly the same as in the Snes9x options. Then they select Project64 from the list, an N64 controller is displayed, and they can go through each button on the N64 controller.
If they have a common controller (XBOX360, PS2 adapter, etc.) then they can select a default profile which configures it for all emulators. If they want to tweak something, then they can do so using the aforementioned process.
Any updates are distributed through a small XML config file which can be downloaded automatically at runtime, ensuring users always have the latest options.
A more technically capable user base is no excuse for an unnecessarily complex user experience.
This is an entirely seperate issue. You should never exclude any group of users through poor design.




