Adding a couple Information keys to enable temporal filters to be run in situ

I’m personally struggling a bit to find a solution for client receiving data that needs to expose TIME_STEPS downstream. The problem is that it doesn’t know a time range from start and further downstream, I need a temporal cache, which should have a certain depth. My current solution is some dirty hack of calling a home-made update time range for each Update(). I guess this solution could be of use for me.