Do let me know.  We're focused on the network i/o testing aspect (per being a WiFi chip vendor) and are intentionally not trying to provide CPU load metrics. (I think netperf provides both.)  A feature we are adding is to warn when we think something other than the socket reads() and writes() have become bottlenecks, e.g. in a CPU constrained system it becomes an "entangled metric" between i/o and CPU though still presents in network i/o units which can be misleading to network device vendors.

Also, many might want to consider monitoring "network power" which is average throughput / latency or delay, i.e. "something good" / "something bad"

Bob