You are asking me to repeat myself but more concisely. The simple answer is that I am not ready to answer your questions right now. I have over 20 documented plugin problems now so I need to see which are relevant to plugin combinations. However any example I give probably should have its own thread. I could give you 1 example purely to illustrate how different parts of the application fail to work together. I have avoided doing so because of all the reasons you already mentioned.
You want
- The advantages over the current modular approach
- Illustrated by common use cases
My objection may simply be about plugin writers using webview/iframe panels instead of making permanent changes to the actual markdown. Thus providing features that cannot be combined with information in other panels.
Maybe needed API variables can be changed for documents not currently in the console. I don't know. I am looking.
So. Please be patient.
Here is an example that includes the spoiler plugin and the outline plugin with userstyle.css and the pdf preview. Does the preview need upgrading? Will it export? Does spoiler have unannounced userstyle values? This is not the thread to discuss it