I'll leave an image of tarek2 answer to stop the loop. (in case the files disappear)
Leave an Ashley ping in case he has the time to give a thumbs up/down for the practice.
Your post comes across as a bit rude and weird!
You asked how to "Stop the Loop" so Tarek2 showed his way according to how construct works and the construct rules but you dont like it?
It seems that you already knew how the "stop the loop" works but you were not happy, in that case, why not start the thread tagging Ashley directly and let him know that you weren't happy? instead of asking users? and Also by doing so, you could have the benefit to ask if any upgrades can be made.
You literary asked the creator of the engine to thumb down his own creation as he is the one that created those rules and restrictions, basically the way it's working, so why anyone will thumb down his own creation?
As Tarek2 showed you this is coming from Construct2 which was released in 2011 more than a decade.
As I said your post is weird you could just tag Ashley and ask him if any upgrades can be made, or even better this sounds like a feature request which in that case you should have opened a request on the "Feature request platform".
If you have a better way to stop the loops instead of complaining why not post yours?
I have also been using the method that Tarek2 posted and I didn't have any problems as it's the only way to stop loops accurately that I found and that has less confusion.
You already complained about (dop2000, Tarek2, and Ashley) not sure what are you trying to archive or what direction your thread is going as it's all ober the place and your replays to users trying to help you don't sound very friendly.
Many times we find things that we dont like on construct so we just open a feature request without making that much drama.
Here the "stop loop" looks like construct works by "Scopes" so it makes sense that will stop the bottom Loop no matter how many stop loops you add to the same event. It looks like you are confused by it should stop by "loops currently running bottom to top" which is different than Running on this "Scope". As a scope can be just one, not multiple on the same event because that will confuse even more.