Assuming you would never want to host any website/client unless his website is using a CDN (my assumption may be wrong) not exposing your server IP.
Thus, you'd be utilizing the Enhance CloudFlare integration to oversee all your DNS records, then enabling DNSSEC would occur directly within CloudFlare, not through the Enhance CP. The issue arises when activating DNS management within Enhance, as this action also enables DNSSEC management for users. This situation can lead to confusion, as users may be unsure whether to utilize Enhance DNSSEC records or those from CloudFlare.
My feature request pertains to having a distinct toggle dedicated solely to DNSSEC within the Enhance CP package settings. This separation would alleviate the concern of unintended DNSSEC activation and provide users with clarity and control over their DNSSEC settings.
OR another way to do it is if Cloudflare integration is Active, this would hide the DNSSEC toggle or better replace them with CF DNSSEC ones