Change all the cloud-mandatory rules to mandatory and see if the story points calculation and the UI are still relevant.
The mandatory issues are those that must be addressed in order to upgrade/migrate to a particular technology, typically API changes, deprecated/removed classes, methods etc. Cloud mandatory are issues that would prevent your application being deployed in the cloud (hard coded IP addresses, use of native libraries, etc.). Personally, I can see the merit in the distinction. In your use case I can see why you would want cloud mandatory issues reclassified as mandatory. Particularly for rules under the Azure folder. I would have no problem with that change being applied to those rulesets. But I think I would want to retain the distinction for the rules in the cloud-readiness folder.
Change all the cloud-mandatory rules to mandatory and see if the story points calculation and the UI are still relevant.