Yes but that's more of a mitigation than prevention. It's an additional step, you have to remember to do it, and under the pressure of the situation you might easily forget to do it.
Could be prevented by more advanced "AI detection", especially on calls from unknown numbers.
It doesn't even have to be based on watermarking. It could be as simple as, "hold on a sec your AI countermeasure was listening and noticed you got this suspicious call, please be aware this may be a scam. Here is what you should do next..."
It doesn't make much sense to tie this to Chrome itself.
If an app or site uses too much bandwidth, it would be better to control this at the OS level, perhaps with a required user notification and consent. Or throttle certain apps.
It's common to set an alert for total data usage, which makes sense so you don't get surprised when you run out of data. That could be extended to watch the usage rate and alert by some threshold, or a projection on the total, like "hey at the current rate, you are going to hit your limit in N minutes".