The silicon of a microSD card is a cut and paste copy of the silicon in a Solid State Hard Drive
Whilst basic
idea of flash memory is the same, I can assure you these are very very different beasts.
At a very very high level you could call it a cut and paste, but the engineering and layout ins incredibly different at the low level.
Also in the case of SSDs the controller is in every case I've seen separate to the flash memory itself.
If it has wear leveling then that will not be true, and I'm not sure it is anyway since there has never been a direct map from logical to physical location on a flash memory device.
If it has wear levelling you are right, but I disagree that such a feature is as common as you suggest.
Don't get me wrong, I'm not flat out denying it's existence, just how common it is.
I'd welcome solid evidence to contradict this, as i've said it is somehting i have been looking into for some time.
Ultimately you about the camera having no knowledge of the physical memory layout, but the way dashcams operate they do not need knowledge of the physical memory if they are using all of it cyclically.
I'll not claim that the Dashcam is aware of the physical layout of the memory, but if it is left to use all of it, and then begin again replacing every file then logic dictates that regardless of the physical order in which it is happening all of the memory is being cyclically used in an even manor. The physical order might is not particularly relevant.
Dashcams cycle by age of file. (there are other occasional factors, but this is true for 99+% of all situations.)
File A1 would come first, and might be written to part 1 of the flash.
File B1to part 4
File C1 to part 2 - something happened here... file is flagged for an incident.
File D1 to part 1 - memory threshold is reached (not full, but nearly so, at least a few MB must be reserved for varying file sizes on new write.)
Oldest file is deleted (A1) an is replaced with A2
Next oldest file B1 is replaced with B2... and the new B2 is slightly larger than the old B2, see above regarding reserved space.
C1 is marked as an incident, and is left alone
New C2 is written over next oldest file D1.
This is significantly over simplified, but (ignoring long term flagged files, if these exist) all of the space is used, and used again in what results in a supprisingly even manner, but only due to the nature of the dash cam and how they operate.
Ultimately, all dashcams i know will in some way replace older files with new ones.
And ultimately this brings with it a kind of psuedo wear levelling.
Not with awareness of number of write cycles of specific memory address etc, but the end result is very much good enough in practise.
Regarding wear levelling, if anyone knows of cards that are available retail in Australia, or readily shippable to Australia, with decent IOPS with wear leveling i'd love to hear about it.
I know they exist, but only in a few fringe cases that are not readily available, or available with sufficient speed.