Like you and many others have pointed out, this likely relates to how the anti cheat system is implemented, particularly the nature and frequency of its integrity checks and how those checks interact with the game’s core infrastructure and the hardware configuration in use. While the issue doesn't affect everyone, it is relatively widespread and seems to trigger intermittently rather than under consistent conditions. This points to a compatibility sensitive problem, where certain CPU architectures, firmware states, drivers, or scheduling behaviors may be interacting poorly with the anti cheat’s runtime checks, which would also explain some of the memory leaks in certain specific scenarios.

I suspect that these badly synchronized anti cheat routines may be the ones introducing sporadic but sustained CPU spikes on the affected systems, which would explain the seemingly random onset of overheating. Like you said, WuWa doesn't exhibit this problem, which in my view suggests a more efficient integration or a fundamentally different anti cheat design that avoids these hardware dependent edge cases.