yeah, has been requested a while ago…
basically, the idea is to load plugins that are required for a particular patch automatically.
last discussion of this can be found here - lazy loading
there is an edge case here, which is what if you don’t have the plugin on your sdcard? perhaps loading a ‘blank module’ in its place, so you know what to go and look for.
the other edge case, is we be able to unload modules that are no longer in use.
this is useful, not just for a users own patches, but also if you download shared patches, - which you have no idea what modules/plugins its using.
anyway… @danngreen is aware of this as a useful feature request.
iirc, the first step was to ensure the modules could be loaded and unloaded reliably.
again, iirc, the change to call this ‘pre-load’ from autoload, was part of this FR.
(so that auto load could be used to mean ‘from the patch’)
so its kind of ‘in play’ I believe… but then again , 4ms are very busy with many FR 
for now, the best bet, if you dont mind an increased start up time is to load all plugins. theres plenty of memory on the MM so its not really an issue..
also the advantage of pre-loading modules is, it will make switching between patches faster - as it doesn’t not need to load/initialise modules (as they are pre-loaded)