Hi Brian,
Just to keep you updated, we have a fix for this problem and we're looking into including it in our next release of the F5 Management Pack. The fix is related to the big3d agent (part of the LTM platform), and with the upcoming release of the F5 Management Pack you will have to authorize the update of the big3d agent (shipped with the F5 MP) on the LTM v9.3 platform. You have this option in the F5 Device discovery user interface in SCOM (or f5mpcmd command line utility). With the new big3d agent in place, the F5 device discovery will correctly process the cpu_info configuration and stats, so you won't see any errors / warnings about this issue anymore.
Thank you for your patience.
Julian