Use orchestration's input bindings in azure storage table for non-orchestrated worfklows

[Protheon]

Hi,
As the title suggests, is it safe to use an orchestrator's input bindings for other workflows that are not necessarily part of the orchestration?
By default, durable functions store orchestration inputs in azure table storage, under the instances table. This seems to be indefinitely persisted even after redeploys, meaning that if we can query it, we can use it for other logic.

Is this an acceptable usage? The only risk that I see, is triggering a task host purge or renaming the task host. From the documentation I see no indication that there is any automatic purge or soft delete on these entities by the orchestration, meaning that they could be used for anything else.

One thing to add is that this would be for read only operations, meaning there would be no change to the binding data.