The issue is no longer reproducible in the ArcGIS Pro 3.2 release candidate; it also no longer reproducible in the current development version 3.3_50738.
Please get in touch with the team as soon as possible if the fix needs to be backported to an ArcGIS Pro 3.1.x patch.