No, DotNetNuke is not fully FIP's compliant.

Whilst historically most of DotNetNuke worked in a FIPS environment , this was not a compliance mechanism we ever coding (or tested) against so the level of FIP's compliance was somewhat accidental. However in 6.1.0 we introduced the client dependency framework which is called on each page request and as it has non-compliant code it meant that none of DotNetNuke could be used. The fix you reference was a change I made to return DotNetNuke to it's pre-6.1.0 level of FIP's compatibility, so it is now possible to install and run DotNetNuke, but there are a few functions that still fail - most of these are pretty edge case and entirely optional (such as using the deprecated filebased caching provider) so to all intents and purposes it's possible to use DotNetNuke 7.0.3 or higher in a FIPS environment without any issues.