Disabled Plugins: redundant?

I was about to note that the installed L2C modules are initially created as "disabled" in the plugins page, and propose that they be initialised as 'enabled'. But then I got to thinking about the deeper purpose of the "disabled plugins" feature, and have come to the conclusion that there isn't one. There is currently no advantage in having the plugin module installed but the plugin itself disabled. I suspect this was introduced at a time when multiple plugins were provided by a single module, but since this is no longer the case it is purely an extra, unnecessary stage in the installation process.

(IMO it's not even massively useful given multiple plugins in a single module. It's conceivable that an administrator might be allowed to administer Wysiwyg API but not L2C, but this seems an edge case to me. Besides which, the Wysiwyg API doesn't currently respect the 'enabled status' of the plugin. Currently all the 'enabled status' governs is whether or not the admin can amend the plugin settings, making it actively counterproductive.)

I propose the ability to 'disable' a plugin provided by an active module be removed; if administrators want to disable a plugin they can just switch off the module or remove it from the Wysiwyg API profile (which is what they have to do at the moment anyway).