Yes, and I can see the use case for that - it is simple to apply and explain, but also comes with caveats....
He is correct, any segment tagged clearance has to merge into the rule decision tree, and which rule wins ?
If the segment tag always wins, it has trumped the other rules.
It also is not compatible at all with Autorouters.
I can see use for a two-level clearance design, where you say
I prefer this clearance/trace width
I allow this clearance/trace width, in tight PAD locations (aka necking)
That rule is Autorouter compatible, and would cover most of your use example too, without the many-mouse-clicks dance ?