Breeze wind charges can randomly start moving one tick late when hit by arrows shot by players

When an arrow shot by a player hits a breeze wind charge projectile, the wind charge may or may not start moving after an additional 1 tick delay from when the damage was dealt. This is evident when shooting stacked breeze wind charge projectiles, where a separation effect can sometimes be noticed.

Steps to reproduce

1. Allow a breeze to fire at an enemy, and teleport its wind charges to a certain location.

2. (Optional) Use a structure block to save the stacked wind charges, so they can be loaded later.

3. Shoot an arrow at the wind charges.

4. Run the command /execute as @e[type=breeze_wind_charge_projectile] at @s run tp @s ~ ~ ~ in chat to stop the wind charges.

Expected result

The wind charges always stop in the same position, as they got hit by the arrow at the same time.

Observed result

Sometimes, the wind charges separate into two stacks. Usually, one contains most of the wind charges. The stack sizes appear to be random.