from what i've seen, THIS SCRIPT, W/CONTINUATION, and STOP all operate on the script, which is just the blocks that can be seen connected at once in a sprite, and would have to have a hat block at the top to ever be ran. any blocks called from it are part of the script, since STOP THIS SCRIPT will stop areas outside a block.
stop this block is similar, but without the sprite rule, it's just the blocks that can literally be seen connected
interestingly, if sprite A tells sprite B to run a script, it's in sprite B's context, but it's sprite A's script.
i think ALL BUT THIS SCRIPT is clear enough, when you STOP THIS SCRIPT, it doesn't stop the same string of blocks in every clone. this means that ALL BUT THIS SCRIPT would get the continuations of all of those.
i don't have much issue with the existing controls for these blocks, and i'm not suggesting changing them, just adding new ones that work based on environment instead, so if sprite A tells sprite B to run a script, telling sprite B to STOP OTHER SCRIPTS IN ENVIRONMENT will stop it, continuations can be grabbed from existing functions, and told to stop, etc
also i think continuations would actually be easier with that dropdown because now that i'm thinking about it, i don't know if continuations normally operate on the script or the block. i think it would also help that it's more clearly related to the stop block and that it subtly points out that the reason it's RUN WITH CONTINUATION and not just a CONTINUATION reporter is that it gets the continuation of the area after that block, and needs a way to do something with it before running it