Ah, so they have been. Found it at https://docs.coronalabs.com/api/library/timer/allowIterationsWithinFrame.html
I was just looking at the wrong place. Thanks!
It would be really helpful for people updating Corona via open source, to use the form at the bottom of any API they change, so we can know what needs to be updated. It’s important that we get as many details about the change as possible. In the past, Corona developers were required to update the documentation for the changes, then the DevRel team would copy edit them. We can’t guess at what should be there.
Rob
@Rob Miracle Noted. 
A writeup on “time transforms”, along with an analysis of the problem, can be found on my last comment for the PR in question, here. Feel free to use and / or adapt it, and let me know if any more details are needed.
Those methods aren’t necessarily exhaustive, but seemed like a good start. 1D noise might be another decent choice, for example
UPDATE : The chart on this page might give some insights into the numbers. In particular, the “half” type is all we can assume on GLES2-grade mobile devices.