[General Questions and Answers] V0latyle:
Apples and oranges. There's no such thing as "root" on a Windows device, or Mac for that matter. Even administrator privileges are limited. Su on Linux can do literally anything. although SELinux can confine root privileged users. By default, Windows does not allow applications to modify other applications' files, at least not without user approval (User Account Control), and Windows does not allow applications to access the memory used by other applications. Yes, some of this can be done with administrator privileges, but if UAC is enabled, the user must approve this.

So, there's one layer of security. It's also worth notiing that there are no bank specific apps for Windows beyond what they use internally, so us consumers are using web browsers; the banks thus require any browser to implement secure methods such as HTTPS.

The major difference here is that on Android, we are talking about apps on the device itself, handling sensitive information on said device, not just displaying a web page in a browser. We are talking about stuff like tap to pay, using a "third" interface on the device (NFC) to send and receive financial information. There's no direct analog to this on Windows, Mac, or Linux - there's no tap to pay, there's no virtual cards, and sensitive information isn't actually handled on your PC/Mac, it's just displayed in a web page. This is why man in the middle attacks have fallen out of use; most scammers dupe the user into installing a remote desktop program.

For the most part, none of these companies, not even Google, is forcing us to use cloud based apps instead of web browsers (which I should point out would work anyway even if the device is rooted). There's a few caveats to this, I won't name specific examples but there are some that will require you to use their app if they detect you're on a mobile device.

Granted, this extends only as far as the limits of web browsers - you can't use Chrome for tap to pay, for example, so if you want the convenience of NFC payment, you have to use the app, and using the app means you are subject to said app's security requirements.

I've tried to point this out many, many times but you continue to ignore it - in this particular case Google isn't forcing anything on anyone. In their view, regardless of whether we like it or not, some features of some of their apps should not be usable on rooted devices. That's their prerogative. When it comes to Play Integrity, they are trying to market an easy to use API that is an accurate representation of a device's security state. They make money when developers choose to use PI; they don't make money off us "power users". So, like any other security institution, they're interested in improving Play Integrity to be more secure and less susceptible to spoofing, because the more definitive the PI attestation is, the more valuable it is to third party developers.

Google is not responsible for what security engines and root detection methods those developers choose to use, nor are they responsible for what PI labels they choose to use, should they opt to use PI. The only Google apps that don't work on a device failing PI (to my knowledge) are GPay and Wallet; all other Google apps work.

You can sign into your Google account on a rooted device. You can use GMS without problems. You can use most Google apps without problems. You can even use Authenticator for 2FA. The one sticking point is they don't want NFC payment to work on "compromised" (rooted) devices - and I'd go so far as to suggest it's not even about root itself necessarily, but rather they want MEETS_DEVICE_INTEGRITY

I can't change your opinion, and if we want to talk about Google/Alphabet in general, you'd find that we agree on a lot of things, but my point here is that we need to be truthful about who is doing what, and I believe you're mistaken on a lot of the facts.