We use them for tests where we a) need representative data that has some sort of interesting format/dependencies that could be tricky (or slow?) to capture in factories, or that we need enough of that writing out ~100s of factories would be a bit nasty to maintain.
I don't think we'd miss them a lot if we didn't have them for this, but they are handy for this. We use setUpTestData and factories or models directly for most of our testing.
That said, I've just written a new tool for exporting a subset of production data for local use (we have a 2TB database but want a <5GB realistic looking dev database, we export a subset, anonymise, maintain FK integrity, install a bunch of Factories for special test cases). I initially started with loaddada/dumpdata but found them inflexible so I'm using the same de/serialisers with custom code around them. That has been somewhat useful, and if that's the level that this compression code is written at I'll probably use it.