Feature Request: Export to Import Converter

[Knighthawk1895]

Is your feature request related to a problem? Please describe.
When designing a large project that heavily relies upon startup files, dealing with exports and imports can get a little messy. There are times when you want certain things to port as exports and certain things to port as imports. Some of the new options in LEX nightlies do ameliorate this issue a little bit but at the end of the day, nothing's ever completely perfect depending on what you're trying to do. I'm nearing the end of a giant project that's resulted in a pretty sizable startup file that contains all kinds of different objects - materials, particle systems, textures, VFX templates, etc. What I've discovered I've ended up with is a big mish mash of exports and imports not wholly optimized. I have big swaths of exports that could be imports that would resolve perfectly fine, but at some step in the process, they were cloned as exports and stayed that way during much of development. Ideally, I'd want to resolve these as imports so I don't potentially end up cluttering memory with same name exports having to compete for which gets loaded when ultimately they're the same thing anyway.

Describe the solution you'd like
Ideally, my solution would be a simple point and right click option. What would happen on selection of this tool is LEX would look at the export, determine what's currently referencing it, then check to see if there's a copy of that same object with the same path somewhere in a startup file to see if an import of that export would resolve. If true, it would then trash the export and create an import with the same name in its place and relink all the references. Ideally, an automated experiment to do this to the entire file would save a tremendous amount of time but I can foresee potential issues that might cause LEX to hang if it's having to do that to literally every export in a massive file.

Describe alternatives you've considered
What I'm doing now is pretty standard practice. If I can determine an export could be an import and be resolved, I clone an import, rename it to the name of the object in question and then relink the references, then run "resolve imports" to ensure that it's resolving properly.

Additional context

Here's an example of a giant list of exports that could be resolved as imports. I can and ultimately probably will convert them manually, but a point and click option would cut the time required to do so drastically.

[Mgamerz]

While I appreciate the idea of removing extraneous exports, I'm not sure I see the utility of this. There is no confusion over which exports get used - the startup file will always win. An export to import converter would be nice (some work has been done on this) , but I'm not sure the reasoning behind this is solid on this feature request. Reducing file size may be a better reasoning.

[Knighthawk1895]

So this is a startup file that's importing from a startup file that loads earlier. Keeping this exports doesn't make a whole lot of since, since, yes, the earlier loaded startup file will win so these exports are just adding unnecessary bloat to this startup file