Since you have autodeploy environment, host profile is the only option.
Add the rules that change device attributes before extracting the host profile from the reference host. After attaching a host to the host profile, if you edit the profile and change the device attributes (for example, mask device paths or adding SATP rules to mark the device as SSD) you are prompted to reboot the host in order to make the changes. However, after rebooting
compliance failures occur because the attributes changed. Because Host Profiles extract device attributes before rebooting, if any changes occur after the reboot, it evaluates and finds those changes, and
reports it as non-compliant.
Whatever you are observing looks expected..