My guess is for distillation, they need to forward the prompt to Anthropic to get the real Anthropic model's response so they can train their own models on it
Improvements in model performance aren't always strictly compute-constrained in a way that makes them reliant on Moore's Law. Open weight models-- in particular, from Chinese labs-- are optimizing model intelligence with less compute. They're "behind" frontier models by months, but as others have noted, it's possible to get Sonnet 4.5+ level performance at reduced cost, today, from open weight labs.
This has been a thing for years, and so much so, that there's an entire TV with a dedicated second screen that shows you ads underneath your main screen: https://www.telly.com
No one rich enough flying what the average person would consider a "private jet" or private plane would be flying VFR from uncontrolled airport to uncontrolled airport. The "ultra rich" are not puttering around in single-engine Cessnas
I do think you're ignoring a huge part of the problem though, and that's software support. Because reality OS is iOS-based, we're likely going to end up with the same limitations, and many professional industries (software engineering, for one) just won't be able to take advantage of the device fully.
Of course there's workarounds (I used GitHub Codespaces for a while on my iPad and went without a Mac, and you could use the desktop streaming available on the headset), but they are no match for the same convenience you get by staying fully within Apple's walled garden.
The issue is more the ubiquity-- when everything from my phone, to Nintendo Switch, to headphones, to flashlight, to laptop use the same cord for power and data, it's a bigger problem than the low spec HDMI cable you plug in once.
Explaining to my aunt or uncle or grandparents that, no, the cable and charger they bought isn't the right one for their phone/laptop/whatever even though it fits isn't ideal. Sure, it might just charge slowly (cue family tech support call), but it could also just show "not charging" on OS X for example, which is just confusing for most people.
It's a real problem, even if tech savvy people are fine with lower charge speeds because we know that the charger/cable/device combo only supports PD profile whatever.
I don't really use YNAB to strictly budget either, but more for tracking as well. Essentially, I budget the fixed categories (mortgage, property taxes, insurance, etc.), move some fixed amount to a savings category, and then leave the rest as "To Be Budgeted".
Then, as the month goes on and some of the categories that didn't have a fixed budget are "over budget", I just move the required money to the individual category to zero it out. Anything that caries over to the next month goes to the savings category.