Look man, the PC guys use something like 8-16 benchmarks for a real assessment (TomsHardware, AnandTech, etc.) and very few of those are synthetic benchmarks. The PC folks don't even use Geekbench and many of them are pretty explicit about an individual benchmark's shortcomings.
Real world use is ultimately the best.
When the Windows PC guys review graphics cards, they typically run 8-12 gaming benchmarks. Some are canned built-in benchmarks like Shadows of the Tomb Raider. Others are scripted play. A few sites will average the FPS from their tested games. There's also the quality-performance dichotomy. It's not just about FPS. If a GeForce RTX 2070 SUPER can feature hardware ray-tracing and a Radeon RX 5700XT cannot while both get similar FPS, there's qualitative difference.
There's also the notion of power consumption, cooling system noise, etc.
That's just a simple example of why simple benchmarks are dumb.
I can run the most advanced CPU benchmarks on my custom build PC but guess what? I rarely use my PC in that manner. The closest I ever get is Handbrake ripping.
By contrast, PC game play with AAA titles will tax the GPU but with different demands on the various subsystems of the graphics card. It's not just about core load. There are a ton of game metrics that aren't captured by a benchmark (load times, latency, gameplay quality, etc.).
Mac benchmarks are especially lame. I think a large part of this is that the people who write these benchmarks (mostly PC developers) don't understand some of the Mac advantages that are more difficult to quantify.
For sure, no one benchmark is comprehensive which is why the PC guys have 10-20 page reviews on a given CPU or GPU.
I'm not claiming that Windows PC are inherently superior but in terms of the benchmarking and review process, there are simply more eyes on the Windows PC hardware process than the Mac hardware process. This leads to some very critical analysis. If the reviewer slips up, he/she can count of an army of review readers to unvalidate his/her analysis within hours.
In the Mac world, we see regular published writers spout inaccuracies that never get corrected.