Actually, the game can run thousands of scripts at the same time without any problem.
The easiest way to see it is to open the first automatic save performed by Alternate Start with ReSaver, for example.
How many active scripts do you have? I have 67 in this save and more than 100 others times and I never had any problem when starting a new game.

The only real problem comes from what the scripts do.
You can execute 100, 200, 300, 500, 1000 ... scripts that, apparently, are INTENSIVE WITH SCRIPT and the game does not have any problem.
But you can run ONE script and ONLY ONE and your game can start to slow down a lot.
Because the real problem is in what the scripts do.

THIS IS THE CAUSE OF THE STACK DUMP:
When a script register for a frecuent event and the script need a execution time superior to the frecuency of the event the game can enter in an infinite loop.
The game are processing the events and calling the function but, when the funtion can not be executed completely, the game can start the acumulation of scripts.
When the cumulated calls count go over the critical point the game make a STACK DUMP.
A lot of people think that get a STACK DUMP is bad but is FALSE.
The STACK DUMP is a protection of the game for try recover the normality. Simply the game stop all the script and start running it again.
A lot of times that is enough and the game start work normally again, because a lot of times, that tremendous spike of scripts are punctual.
But if the cumulated calls count start up again and go over the critical point the game make another STACK DUMP. And another and another and another...
And that mean a problem in one mod. Is not a problem in the game.
The game make the STACK DUMP for auto restart itself and try recover the normality.
But can not made it if a bad script from a bad mod is causing problems.

My test can create Stack Dump when start the test and probably generate a STACK DUMP every time you try stop a big test.
IS NORMAL... not worry... That not mean a problem in the game or a problem in the mod.
Because ONLY ONE STACK DUMP is not a problem.
When my test starts, 3200 events are sent and, sometimes, the script engine can not accept it and generates the STACK DUMP.
But after the STACK DUMP, the game regains normalcy and processes all events without any problem.
You can activate the registry in your Skyrim.ini and see how the STACK DUMP is generated and how my test runs without any problem.

The STACK DUMP can NOT make PERMANENT DAMAGE and can NOT break any script of any mod.

The game suspends all the scripts before doing the STACK DUMP and restarts them EXACTLY in the same point.
A script can NEVER lose a line of code for a STACK DUMP because the STACK DUMP is a game protection to RESOLVE a problem and can NOT cause another problem.
Normally, my mod generates a STACK DUMP when the event is sent to stop the test. But ALL events receive the stop command AND there is NEVER a pending script running.

If you get a large amount of STACK DUMP or get frequent STACK DUMP are caused by a problem in a mod.
Of course, ONE STACK DUMP and ONLY ONE are not a problem, can be caused by a punctual overcharge in the game.