as stated in the topic i linked on your other thread, mod sources and target are relatively expensive.
so having a huge number is going to cause issues, if i was doing it, id be probably be looking for a different way to achieve something similar but a bit less generic, and so cheaper to implement.
as @jaffasplaffa pointed out, the thing about axoloti (and will still be true of an H7 version) is that its not a general purpose computer, so building 'generic' patches is not really the best way to tackle it,
rather you'd be better off to create a number of patches perhaps with variations ...
looking at this a different way
a VST on your desktop has to supply things like mod matrix because, as an end user, you cannot modify the code... you cannot change the code to say Y axis should now go to wave shape rather than than filter cutoff. so it has to be 'soft coded' to allow this flexibility.
this is not true of axoloti, you have the ability to change the patch, to change the code!
so you can create variations that behave different.
so what might be two different presets on a VST, can be two different patches.
once you get used to this, it can become pretty liberating for a few reasons
a) you don't have to build huge complex patches, you can aim to build smaller things quicker.
b) you are not limited in your patches by some predetermined design decisions.
(b) can become quite a pain, when your patch becomes much larger... because you will keep hitting your head against various brick walls, either due to resources, or ones imposed by how you write the patch.
also... i think axoloti OS 2.0, is going to bring some interesting new approaches, given patch modularity has changed... an area I look forward to exploring