They do mention that the change is meant to reflect how real world programs handle various types of workloads.

> In Geekbench 7, a workload only runs in multi-threaded mode if the task it models actually runs multi-threaded in real applications. For example, the HTML5 Browser test isn’t included in the multi-threaded suite because web browsers are single-threaded (or lightly threaded).

Yes, they have a valid reason for the change. But I think it's still making a tradeoff, and has a clearly identifiable downside because the content of the multi-core test suite is no longer as closely aligned with the content of the single-core test suite.

(One could just as easily argue that the single-core test suite ought to exclude any task typically done with multiple threads in real-world usage.)