For instance I needed driver files loaded onto an XP system for an older Broadcom modem which only had them through windows 2000. You would thing such driver files should run in XP anyway, but no, the install program refused to load them with a statement that the system was not windows 2000. Instead however, I was able to right clk on the install file, set to use w2k compatible, and the program ignored it was on XP, loaded the driver files, and they worked great in XP. So, your suggestion would need to add if they worked using "compatibility mode" also, and even that might not cover it since an original load of a windows version might run the program, but after a service pack or two have been added, it might not run under that version anymore. So, you'd also need to add which service packs it would work under for each system.
It's a good idea, but a lot of stumbling areas along the way that would need to be addressed to make it feasible.
I get Download Notices from CNET about programs I have downloaded, (ie. Registry Cleaner, Java, Acrobat, Quicktime...) What I think there should be is an OP System rating at the bottom of each notice. Computers out there use different operating systems from XP, to Win7 to Vista, to Win8, etc.
IF an upgrade comes out, and I have an XP computer, the upgrade may be targeted for Win7 and Vista users and have nothing of use for WinXP. at the bottom of each upgrade notice CNET should have a strip for the OP systems with a 0, 1, 2 rating next to it. 0= nothing of use for that op system, 1= something of use 2 = vital changes..
Such as [ XP=0 W7=1 Vis=2 W8=2 Lin=0 Osx=0 ]
That way each person will know if they should bother with that upgrade.

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic