ConfigMgr Bitlocker Management

for a co-managed devices, if you set the workload to Intune , it will use Intune and not save keys to ConfigMgr.
In ConfigMgr, features are being added with each release of ConfigMgr. you can see lot of new functionality added for Bitlocker management when compare with MECM 1910 to latest ConfigMgr version. with ConfigMgr I can see very few similar MBAM GPO's functionality are missing however, the BitLocker management settings are fully compatible with MBAM group policy settings. If devices receive both group policy settings and Configuration Manager policies, configure them to match.
https://docs.microsoft.com/en-us/mem/configmgr/protect/deploy-use/bitlocker/deploy-management-agent

not sure about your requirements and I can see some similar functionality in MABAM are not  in Intune at the moment like you require to use PowerShell script to save the key to Azure AD when the device is HAADJ etc..
https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises#powershell-examples

Microsoft BitLocker Administration and Monitoring (MBAM) End of Life :
https://support.microsoft.com/en-us/lifecycle/search/18037

please check comment section here as well : https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/bitlocker-intune-and-raven/ba-p/1048033