Hoping we can get some clarification from a Check Point employee as attempts to clarify through local SEs haven't resolved it for us.
Similar to sk172623 and https://community.checkpoint.com/t5/General-Topics/CoreXL-option-disabled-in-cpconfig/m-p/73820, we have seen ongoing issues in multiple versions (and environments - at least four so far) where CoreXL configuration disappears on reboot or with an upgrade.
We were told that PRJ-20160 was fixed from R80.40 JHF 100, which seems related to sk172623 above, but we've seen the issue in R80.40 JHF 125 on CG IaaS on VMware, and more recently in an in-place VSX upgrade from R80.20 to R81 on HPE server hardware (open server).
We're still deploying the originally suggested workaround from TAC (chattr +i $FWDIR/boot/boot.conf) to make boot.conf immutable and prevent these issues.
I've never seen PRJ-20160 appear in any of the release notes. We were told in December that the issue was (again...) fixed in R81.10 - but there's no obvious relevant items in the release notes.
Is there a clear indication that this issue is resolved in R81.10?