ID 483100 - Using an export preset that references an ACES colorspace in a nuke-default project results in an error on export

Problem summary
Using an export preset that references an ACES colorspace in a nuke-default project results in an error on export

Customer reported version
hiero.12.1v3

Customer reported platform
centos7

Steps to reproduce
1. In NukeStudio/Hiero, Start a project called 'projectA'.
2. In the Project->Edit Settings->Color Management, set "OpenColorIO Config" to aces 1_1.
3. Load in a clip and bring up the export dialog.
4. From the export dialog, choose the "Process as Shots" and the "Transcode Shots DPX" preset.
5. Change the Colorspace knob on the task to any ACES-named colorspace, such as "data (Utility - Raw)".
6. Export or Close the dialog, making sure to save the preset.
7. Close projectA, and start a project called 'projectB'.
8. In the Project->Edit Settings->Color Management set "OpenColorIO Config" to nuke-default
9. Load in a clip and bring up the export dialog.
10. From the export dialog, choose the "Process as Shots" and the "Transcode Shots DPX" preset.

You will see that instead of "AlexaV3LogC" or something specific as the Colorspace value, the value is set to "default" because it's the first item in the combobox.

Expected behavior
The value in the UI that the editor sees should be the value that the ExporterTask actually uses.

Actual behavior
The value in the UI is not the value that is used, when the UI cannot satisfy the preset, the preset value is maintained but the UI shows the first value in the combobox, usually as "default"

Workaround
There is no available workaround at this time.

Reproduced by Support in:
NukeStudio/Hiero 13.0v3 - Windows 10, macOS 10.14
NukeStudio/Hiero 13.0v1 - Windows 10
NukeStudio/Hiero 12.0v1 - Windows 10
NukeStudio/Hiero 11.0v1 - Windows 10
NukeStudio/Hiero 10.0v1 - Windows 10
NukeStudio/Hiero 9.0v1 - Windows 10, macOS 10.14

Earliest version tested
NukeStudio/Hiero 9.0v1 - This issue appears to be in all versions of the product