The upside to this idea is clarity. The downside is loss of brevity which people naturally gravitate towards. "1080p" or similar explains what's happening for 99% of titles. 1920x1080 doesn't add anything but doubles the amount of communication bandwidth. When your audience is very much the layman rather than an engineer reading a technical document, choice of language will tend towards the vernacular.
This is why despite my petitioning, 4K is always presented as 4K and not 2160p, even though 4K isn't even defined. It's assumed to be 2160p. No-one targeting the average Joe is going to choose '3920 x 2160' over '4K' in describing an output resolution.
If you want accurate data in an article like this, you need to wrap it in a language-friendly presentation, meaning concise. You could do things like give a number as a percentage of 3920 x 2160 pixels drawn and quality.
"Hellblade 2 renders 0.20 work and 0.25-0.35 drawn"
Brief and informative, meaning 20% as many pixels of a 3920x2160 display are calculated and 25% to 35% of the pixels are drawn. However, that doesn't read nicely without being 'trained' to read it, whereas "xxxxp" is now naturalised.
I doubt a site making something up on their own and trying to normalise it won't get very far, and I doubt it can be considered worth the effort to try. The negatives of short-form reporting using the current language are fairly niche and most people don't care. The fact console-warriors weaponise data isn't DF's responsibility so long as they aren't deliberately (mis)representing the data to help gain hits from eager console warriors looking for ammo.