Describe the bug
All transforms ignore the visible history field so far.

To Reproduce
It's best visible in the transforms3d demo of api_demo where everything on screen is logged only once but has changing transforms over time.

Expected behavior
For the demo in particular it's natural to expect traces of the planets as they go

Additional context
The underlying issue is that the transform cache doesn't know anything about visible history so far. Fixing this might be a bigger undertaking as it means that transforms shouldn't be queried & computed via the object path alone