Installed Windows 11 with TPM Disabled? Expect an Ugly Watermark on the Desktop

It's a lot of articles.
Then it should be easy to find at least one that can actually substantiate the claim, right?

Are those systems bypassing TPM? Running the latest update and not Insider preview?

Correct. They are all running 22H2, build 22621.1265, which is what you end up with after installing the February 2023 cumulative update. Some of them have TPM 1.4. None have TPM 2.0

Because laziness? The screenshots are of old builds when Microsoft has attempted this in the past. It's reasonable to assume they'll attempt it again.

Can't find any proof, so making excuses instead. Got it.
These Linux celebration posts are completely off topic.
I think it is completely ok to point out that this watermark is due to Microsoft being Microsoft, and nobody else treats their users in that way.
This is visually similar to the watermark you get when you haven't activated Windows with a valid license.
I think it is more alike the Windows 10 Education watermark which existed from RTM to Anniversary Update.
We've established that the watermark he is seeing is because he is running an old version of Windows 11
If you find even one single person with a watermark who is running 22H2
Then it should be easy to find at least one that can actually substantiate the claim, right?
Not necessarily, the relative lack of reports could also be due to survivorship bias. If 22H2 upgrade is blocked on 22H1 systems which qualify for the watermark, then only people who directly installed 22H2 will see it on that version, and almost all user reports/screenshots will be from 22H1.
This seemed inevitable that the fundamental flaws of TPM would be set on stage finally

New Vulnerabilities Found in TPM 2.0 Library That Could be a Potential Threat to Billions of Devices

A pair of new vulnerabilities have been found in the TPM 2.0 library by cybersecurity company Quarkslab, that have security experts worried, as both of the flaws have potential far reaching implications. The two vulnerabilities go under the CVE identifiers of CVE-2023-1017 and CVE-2023-1018, where the first one allows for out-of-bounds writes, whereas the second one enables out-of-bounds reads, also known as buffer overflow vulnerabilities. This in itself might not sound particularly concerning, but as both can be triggered from user-mode applications, they're a pretty big deal, as it would enable malicious commands to be sent to a TPM 2.0 module, which could in turn enable malicious software to be installed on the device with the TPM 2.0 module.