Final Cut, Adobe CS and a few other major products are the exception to the migration, not the rule. I've spoken to people who used to work on Final Cut. It has one of the largest codebases that I've ever heard of. Plus, Final Cut wasn't done in Objective-C and Cocoa. It is a C++ application with a completely custom UI, done by Macromedia over a decade ago. Its not even a full 64-bit application yet.
This specific psychographic is well known for spending money on products with social cache. This social value is partially driven through the "wow" factor of Apple's secretive product release cycle, meaning that developers who don't like it can go lump it and head over to developing for Microsoft or Google's platforms.
When you say they sacrifice "users," you're right, but those users aren't priority #1.
EDIT: Parent comment was deleted. Was about how inconsistent product release cycles and roadmaps degrade user experience.
LogicPro - the migration from a dongle-based system to a non-dongle system was an utter nightmare where some people were able to maintain their old license and pay the upgrade price while others couldn't.
PPC -> Intel - the migration in driver architecture was a nightmare across the entire Apple ecosystem. "Better/faster/just works" did not apply here at all. As a classic example: the version of Final Cut released shortly after the architecture switch was unable to run natively on Intel. Shortly after the Universal Binary version was released, Apple broke compatibility with After Effects plugins and instead replaced it with FxPlugin and once again caused a huge disruption.
So yes, it does in fact seem like the sort of thing Apple would do.