Improve the functions registry efficiency

There seems to be a great deal of conflict surrounding the registry. Much of it has to deal with the efficiency level of the registry. I have two ideas that I believe would help increase registry efficiency. Granted, there are people here who are much smarter than I.

The registry currently acts like a preloaded cache. (Well, actually, it is a preloaded cache. Anyway...)

I propose two things:
1) We quit preloading the registry. When we search the DB, if the item we are looking for is there, good. Otherwise find it. Since practically all contrib modules abide by Drupal naming conventions, the search should 99.99% of the time be a fast operation. e.g.: wysiwyg_load_editor can be found in a file that starts with 'wysiwyg' in a folder that contains 'wysiwyg' Most functions that start with drupal_ can be found in the includes directory. Using this little piece of information should allow us intellegently search for what we desire. (Then add it to the DB.) This basically turns the registry into a regular cache. This should help cut down on the size of it.

2) We cache not only the location of functions, classes and interfaces, but more importantly which menu items (note: I'm not saying path. Rather, I'm referring to the array in hook_menu.) cause which files to be included. For instance, visiting /podcasts/archive might load the particular include files needed by views, cck, date, etc. By checking the DB for our serialized or delimited list of files to include, we should be able to load only the files that are routinely needed by this location. If changed / unlisted, Drupal would save the list before terminating. This should provide a low memory/processor/db intensive means of quickly loading needed files.