From the article:
Normally you don't need that to read and write to diskettes: it's only for things like handling floppies with formats other than the basic PC- and Mac- 1.4MB "high-density" format, or handling copy-protected disks, and so on. This sort of stuff won't work if you use a USB floppy drive, anyway: their embedded controllers only understand standard formats, and so can't handle classic Mac or Amiga double-density disks from the 1980s.
That's actually conflating two slightly different issues. The PC style high capacity formats such as DMF and XDF generally either crammed more sectors on a track or used a higher than normal number of tracks.
The former reduced the inter-sector spacing demanding higher tolerance in speeds and timings, and so was only really suited for single pass format-and-copy use such as software distribution. They were decidedly "dodgy" for general purpose use especially between machines, any slight mistiming could cause the end of one sector to overwrite the start of the next.
The extra tracks were of a "this is out of spec but works on most drives and disks" thing, relying on the fact most drive heads could physically seek slightly past the track 40 or 80 position and most disks still had usable media for another couple of tracks. Fine, until you encountered a drive or a disk where those assumptions didn't hold.
The Mac and Atari high cap formats worked differently: those used additional sectors per track but only on the outer (longer) tracks. Timing and spacing were preserved by physically spinning the disk slower when accessing those outer tracks. It is not a question of software or even firmware - a standard PC floppy drive is mechanically incapable of altering speed to read those disks.