Okay. That content is produced by Adobe. Any questions concerning applicability logic or diagnosing why a package reports as NotApplicable when that's not expected would need to be directed to Adobe, as they are solely responsible for that content and its behavior. But, in short, I've rarely seen a package reported as NotApplicable when it actually was, so the better question here is not "What's wrong with the package?" but rather "What's wrong with the target system(s)?"
Note: You cannot edit Applicability or Installed Rules for an MSP-based package because those rulesets are not used. The detection logic is contained within the MSP itself.