They do like "ls /sda0/dirty-tracks/ | xargs -P 1 dd if=/sda0/dirty-tracks/{} of=/dev/sda{} size=512M && rm /sda0/{}", but onboard the disk, not on the host, and that's both wildly slow and imcompatible with anything but super light or niche use cases.
If only they at least used a NAND flash for that staging or at least coordinated with the host system, but no, HDD industry chose not to cooperate with anyone and to hide the fact that some disks are DM-SMRs.
Think of SMR as "fast tape with random reads" rather than anything like a CMR product.
The way it would work is:
* The underlying disk would do sequential writes only, in 1Gb blocks, rather like a log filesystem.
* The large block size enables much better information density due to being able to tolerate far more errors.
* Random reads within blocks can usually be done - but occasionally most or all of the whole block will need to be read to decode the data.
* A small capacitor+disk momentum ensures any writes that happened before a power failure can always be completed - either to the real disk or to flash.
* The OS still only sees 4k pages - versioning, packing those into 1Gb blocks, mappings and garbage collection are all handled inside the drive.
If the disks were host-aware, Linux (and preferably ZFS) could handle host-aware SMR disks non-catastrophically, and SMR disks were part of a separate product line with prices and capacities that make some sort of sense when you compare with the CMR line, I'd be all over them as cold storage, or just treating them as (re)write-once-read-many drives.
But it's clear WD and Seagate don't care about the consumers. They're just a rounding error in comparison to B2B sales, especially given the current times.