Honestly it sounds like you are making a mistake in how you use MOCs. Maybe I’m misunderstanding you but it sounds like you are adding every note to a MOC. In that case you are effectively recreating tagging.
I don’t update a MOC with every note I add to my ZK system, only those that represent key entry points to various topics within that MOC or are notes that don’t really fit into any other note or MOC. (so there’s at least one link to the note from somewhere, and that link probably gets refactored to somewhere else as I add more notes on that topic over time)
If you are simply linking from the MOC to every individual note you are kind of recreating folder/tag hierarchical systems which is an anti pattern. You should focus on building up a dense network of interlinked notes at the “low” level among your evergreen notes then allow MOCs and similar index/outline notes float above them and point to the key entry points.
Then when you use the MOC you are following a link from the MOC to an entry point into a topic, and then once you are in that topic within an evergreen note you are navigating from note to note within that topic via inter-note links.
Analogy: You are playing an FPS game and the MOC is the top down map view, but once you click into an area you switch to the FPS view and navigate from room to room (note to note). Then periodically you switch back to the map view and jump somewhere else.
Adopting this approach is what brings fluidity to the process.