You're really not making a lot of sense. If you have 100 development and 100 QA DB2 subsystems, you should manage them as two service classes -- one for development and one for QA. The whole point of WLM is that you group similar work into service classes, prioritize the service classes, and manage the system as a whole. WLM is not designed to manage resources in the way you want to. Furthermore, if you have multiple LPARs in your sysplex, all of them are managed through one WLM policy -- so you could potentially be impacting a lot of work through your quest for the impossible.
If you really decide you want performance data on each individual DB2 subsystem, that is what SMF data is for. If your site uses MXG, I'd start with the ASUMCEC and RMFINTRV reports to get a feel for what's happening overall with the system, then dig into anomalies on a case by case basis.
However, you simply cannot manage "hundreds" of subsystems on a one-by-one basis. Your system overhead for WLM will go through the roof, workloads won't meet goals, WLM will be very slow to correct issues, and you'll be lost in a flood of data that is too detailed to make sense of.