eth_syncing returns incorrect start height

[peterargue]

Problem

I was debugging a data issue with a partner and they resynced their node from genesis by deleting the db, and starting up with --init-cadence-height=211176670. After a few minutes of syncing, they queried eth_syncing, and the returned data showed the starting height as block 3. They were able to query blocks 0-2 and received data back, so it appears that there is an issue determining the start height.