Are there any plans in the future to correct this part to work with animated objects?
It is fixed internally, but we are waiting for a 3rd party to send us a license of their product to fix another bug before we release v2.0.2.
In the mean time, you can work around the problem by adding a pass-through (disabled) ToSpace or FromSpace operator after the InputChannel:Position and pick the same object used in the InputGeometry node to create a dependency. (The bug was that the InputGeometry was not processing the notifications from the reference node correctly).