Thanks, Tim, I'm glad you find the wiki useful.
As for tapping into the communication between MAX and the controller, I'm not aware of any possible ways to do so. Frankly, I'd be surprised if it was possible. You can use the NI System Configuration API, though, to programmatically read information from target devices. I can't remember if CPU Load is part of the available information?
Additionally, you might find this interesting: MAX uses the NI Discovery Protocol (amongst others?) to communicate with targets. That protocol is based on UDP to allow for finding targets and configuring IP addresses across the border of TCP subnets.
I started reverse-engineering it years ago; whatever I needed back then (mostly only setting IP addresses) can be found here:
https://gitlab.com/hampel-soft/open-source/ni-discovery-protocol-api-for-labview/-/tree/feature/0_im...
I can't remember seeing CPU loads in the UDP messages, though. I believe that kind of information is not sent via UDP but part of the TCP communication (i.e. the connection made after configuring PC and target so that they both have IP addresses in the same subnet).