It does matter, because that Google integration didn’t happen by magic. Whatever the site is, they chose to do things that way.

The only way Google stops things like this is if they get actual pushback, and the only realistic way to achieve that is to make the people using their service reconsider.

Also, the answer to your actual question is no. There’s definitely no way to block people from using any particular characters at the kernel level.

What you seem to be asking for is a way to absolutely forbid all software from writing certain characters to files, and/or from reading those characters. Aside from requiring that the kernel inspect all data in detail before letting other software have it, which would slow everything way down, it would prevent anyone from reading or writing binary data which happens to contain those sequences of bytes by coincidence. Binary data includes things like the programs which make the system work, so blocking those characters would be terminal

It ought to look like a bunch of □, which is the glyph generally used to indicate that the font has nothing to represent the character.

Specifically you’d expect U+25A1 □ WHITE SQUARE