Sorry, no workaround available. This issue still exists. Please reach out to your Customer Success Manager to hopefully get even more outreach
I understand SailPoint trying to put default functionality in place to speed up our implementations, but if they are not allowing to overwrite this default configuration all they do is put limitations on their own functionality.
I see a pattern of SailPoint making this (in my opinion) mistake. For other examples, I did see announcements like (only paraphrasing):
- “We notice many organizations require certain identity attributes so we will add them for you directly, and oh yeah, you are not able anymore to remove those identity attributes if you actually don’t need them”
- “We allow you to configure which identity attributes are visible for approvers, we notice that many organizations want the email address visible, so we will add it for you directly, and oh yeah, you are not able anymore to remove this configuration.”
It all boils down to: One size fits nobody. Keep supporting configuration is good 
Kind regards,
Angelo