I always enjoy these articles and find them useful and informative for what they do, which is to attempt to define some quantitative measurements and then optimize systems to those measurements.
I'm sometimes afraid to share them with less well versed friends who just want to blindly follow a build though, because the systems engineered this way can only be as good as the measurements they are geared to, which for many may not reflect the total experience of use.
To exaggerate a bit, these analyses can be a bit like a new car review that goes in to exquisite detail on the top speed achievable (down to 1/10th of a mph!), while failing to weigh in at all on acceleration, storage capacity, and luxuriousness of the interior. This is how you get to system builds that are stingy on SSD capacity or even go without; have less RAM than they could; and have aesthetic qualities that some may find out of place with the budget. (the fact that these things do not increase frame rates by 3fps does not make them unimportant over real world usage of a system for a few years of varied use.)
I don't have an easy solution for this. Enthusiasts will pick up a lot of the information they need by reading other articles on this site or elsewhere. I do also want to say I really appreciate that Tom's actually builds these entire systems, with the result of occasionally encountering unexpected physical, cooling, or other incompatibilities. That's valuable info too and much nicer than reports that pick parts on paper but never actually verify they all work together the way you'd expect them too.