Moving blocks auto-saved saved before crash or copied by /clone command do not revert to regular blocks

Updated description by @unknown

Steps to reproduce

1. Set up two pistons on a fast clock circuit pushing a row of blocks back and forth between them.

2. Clone the contraption to a new location.

3. Repeat step (2) until the row of blocks between the pistons get cloned as moving blocks rather than the original blocks.

Expected result

One of the following

• You never get cloned moving blocks in step (3), or

• The cloned moving blocks in step (3) are linked to the cloned pistons.

Actual result

The cloned moving blocks are linked to the original pistons from step one, i.e. the /clone command copies exact tile entity data instead of relative tile entity data. When you activate the original pistons, the cloned moving blocks animate, and when you break the original pistons, the cloned moving blocks revert to their parent block type.

Note

Based on the original report and world save, it might be possible to reproduce this during chunk loading rather than cloning, perhaps with moving blocks being pushed across a chunk border, but I was not able able to do so in brief testing.

Original summary
When piston pushed block isn't rendered causes stuck pushing or pull when many block while loading the world.
Original description
When piston pushed block isn't rendered when loading the world causes it stuck push and pulling block or when you traveling too far cause it will not rendered redstone is running for piston is pushing loopily.