Apple usually provides warning before removal. For example, when they decided portions of Transmit were unacceptable, they asked Panic to change them before deleting the app.
Panic by far and away isn't an "indie developer". In the Mac dev space, they're pretty big.
There have been countless posts on HN from smaller devs getting their apps immediately pulled upon an update review for something they got no warning for.
Panic isn't a tiny player, I agree, but they're not Uber. there's a possibility the human reviewer assigned to its case hadn't heard of the company. If I were a reviewer and I had no personal experience with the app or did not immediately recognize the name, I'd be inclined to treat them just like anyone else.
I would not be surprised if the big hitters are not already tagged as such when the reviews get sent in. Whether there's something as small as a tag for the reviewer to know, or even a separate queue, I sure as hell can bet they go through an expedited and streamlined review process for their updates and such. They're the bread and butter of the App Store, so it's in Apple's best interest to treat them well.
Panic's warnings were in good faith. Cabel's team clearly thought something was permitted, and was simply told "no, you misunderstood" by the review team at Apple.
Dash might be a better example. The account generating fraudulent reviews was contacted before apps were removed from the store. It's entirely possible that Apple screwed up by not communicating with the account used to publish Dash, but that's not what I'm arguing here -- I'm saying that even in clear cases of fraud, Apple usually talks to the developer first.
https://panic.com/blog/transmit-ios-1-1-1/