I was at Windows Phone (WP7/8 days) when “RCS was just a couple of years away”. Good thing I didn’t hold my breath - it didn’t seem to me then that there was any path to success and I was on my first job as a 20 year old.
Google hasn’t managed anything with RCS other than deploy it for their own messaging app that talks to their own infrastructure. The fact that the app uses RCS is an implementation detail - could just as well be carrier pigeons. Doesn’t matter because it isn’t cross-carrier interoperable.
The carriers all moved from Circuit Switched SMS signaling to SMS over IMS (LTE onwards) for interoperable SMS. IMS is the layer under RCS (created originally for cable set top boxes - go figure).
This is basically SMS over IP which means your device is doing all the legacy stuff like 7bit ASCII encoding to pack messages into 160 characters etc. These requirements won’t go away because, the moment a carrier tries to do cross-carrier interop there is a whole sea of legacy translations that would have to be managed by the message originating carrier. This would require real-time figuring out the capabilities of a receiving carrier based on phone number homing. It’s a massive undertaking that’s $$$.
On top of this The carriers all fought including E2EE in the spec to avoid picking a fight with the government. So anything Google implemented is DOA.
RCS has failed.