This is tricky as it is unpredictable and easier to see in a vm, but I have seen it on a native Win10 x64 1903 host. I guess it is linked to performance which is why it can be tricky to repeat.
For a poc, I do a simple write 0x00-0xff to a buffer (stepped through holding F8) and then a check of the buffer via F9. The following gif (apologies if not clear, should show the loop and you can clearly see in some instances al isn't written to memory. This is an extreme example, sometimes it's a single byte and sometimes not at all. As a point, in this instance I have cleared the memory first but if memory contains a value and the bug happens it isn't overwritten. Poc is attached. If you want to repro please try and test this in a vm, hopefully if you give it a few goes it will repro.
As a side note, I haven't got this to repro using animate, but I can reach similar behaviour from an external app doing sendkeys in a loop, where I lower the delay between each key sent. In the latter instance I saw the debuggger try and execute the second byte of the 7 byte mov instruction.
Happy to try and help with any more details of course.
OK, try this poc, Start x32dbg, Set a break so you can see the loop working like above. Then run this simple .net app. It will send an F8 every 100ms and this should work fine. Change it to send F8 every 50ms and on my native host it should show some corruption like documented above, i.e. will end up executing mid x86 instruction.