Hi Rick,
for new request/feature, please use new post. In such case it will be easier to track requests and other people will find them faster.
Generally, this feature you are talking about called indent guides and have nothing to do with scopes. It just shows "indent" positions corresponding to tab sizes. It happens by chance, that it matches scope positions in your case (because yours code is aligned). It is not a unique feature of HE but something, that is common and exist in some other editors, so going here against "standards" can lead to negative feedback from users, already used with a feature in other editors.. Also for matching of the scopes, you already have nested levels + current scope highlight and in 1.50 paired colored braces.
In addition to all mentioned, calculation of guides positions is very intensive for drawing (they done synchronous) and coding there is rather complicated. So, for this is not a minor change.
About requests themselves:
1) because, as I said feature is indent guides but not scope guides, visualization is OK there, and matches how this done in other editors. While keeping nature of the feature same and trying to recognize situation of formatting indent will be mostly impossible. Can you write formal rule: when to draw guides or not? This will help.
If creating of the new feature like scope indents, this will work, but because there are already several features simplifying scope recognition, it can be too much and maybe not really necessary.
2) here, I think can be done something. At least I see that in N++ this is done like you have requested, so to be standard, can be done...
I will note both requests as ideas for improvement. Feature 2 most likely will be implemented, feature 1 need more detailed discussion/logic model.
In any case both features will go in 1.5x.
BR, Alex.