Thanks for pointing this out @GregP . I just created a calculation property from the API without using my workaround. I can confirm that this works as expected now.
I just wish the folks at HubSpot would have confirmed that this is an issue, communicated an ETA on the fix, and informed us when it was fixed. Oh well, I’m glad it’s fixed.