Yeah, I saw that too, but decided that 320MB/s average speed for a 10TB array wasn't even close to being realistic.
Was the parity check tuning plugin installed during the initial build of parity?
If it was and it paused the initial build and you've reset the system, then it never completed and during a subsequent check (with it installed or not), then the errors would be expected