Let's say you change some attribute and the name of a model, Django simply does not recognize it, nuking the whole attribute

It’s not the back and forth, it’s that a migration in b that requires the post migrate step from a will fail if both migrations are run in one shot, (say, because you’re bootstrapping a new dev or test db) but it will work when done incrementally (such as during development or deployment).