For at least Ruby, this is at least true. However, the time that you’re referring to is extremely hard to manage and coordinate. The creation, destruction and lifetimes of a single object are not the same for each execution of a given program on every device. This is before you try and consider multiple objects.
One of the key goals of Sonic Pi is deterministic execution. This means that the same code should always produce the same sounds - regardless of when it was executed and on which machine.
In my opinion we need to be working with time-series immutable data (which also includes functions) with the creation of new information always being atomic from a world perspective. Old values should still be available for as long as necessary. Take a look at time series data stores or something like Datomic to see where we’re headed here 