I had another thought.
I know you use Photoshop in your test suite, definitely keep that I use it everyday as do a lot of other people.
Usually your CPU test rig has a high end video card so rendering is not an issue.
I propose the opposite. With the advent of on CPU video such as Llanos and HD3000. Why not do a series of 3 tests for comparison.
First with a high end discrete video card,
second with an ancient video card, and
third with the on CPU video.
The 1st test would let the CPU fly,
the 2nd would gauge whether a given test is CPU or GPU limited and the
3rd would choke the CPU and check if on-CPU graphics is a viable option for a given user.
I know, I know with all of the tests I am proposing each monthly review will be obsolete by the time testing is complete and published. But as an engineer I know how to configure tests to SEEK and DESTROY any potential weakness that will lead to a possible failure. My engineering professor was the famous Russell Johnson that wrote 'Statics and Dynamics' the text that is used by 80% of engineering students in the world. He taught me that "Engineering is easy. Things will always find the easiest way to break, look for the weak spot and design it so it is just barely strong enough."