No, that wouldn’t make much difference. I don’t think I’ve seen a real world attack via SMS that even bothered to “forge” the from-field. People are used to getting texts from unknown numbers.

And how would you possibly implement this supposed “caller-id” for a field that doesn’t even have to be set to a number?

Blaming the victim solves nothing.

Scamming is a rapidly growing industry that is becoming more professional and specialized all the time. Anyone can be scammed.

To quote the most salient post

The app doesn’t provide client-side scanning used to report things to Google or anyone else. It provides on-device machine learning models usable by applications to classify content as being spam, scams, malware, etc. This allows apps to check content locally without sharing it with a service and mark it with warnings for users.

Which is a sorely needed feature to tackle problems like SMS scams