Shadowfax,
The problem is Apple HAS TO afford to stay ahead of the hackers. They have to break the unlocks. They are contractually obligated to ATT to keep the phones exclusive, they not ATT are the only ones who can achieve this, ATT is going to be all over them to do it and keep it done.
So, it's a contract they have no choice but to meet the terms of, so I support their actions to do that. But I doubt there's much if anything contractually obligating to keep native apps off the iPhone -- except perhaps anything that uses ATT's network. But an iTunes remote control over Wi-Fi? A native-app to-do list? ATT is only care about this to the point that messy non-network native apps might crash the iPhone, cause software conflicts, etc. And their not going to care much because you're still in a contract with them whether your iPhone works well or not.
The unfortunate outcome for someone like you, someone who has hacked for non-native apps but is with ATT and has not unlocked, is Apple is not going to care. In order to break the unlocks, which they have to do by contract, they are going to lock that thing down hard. Which means you get left out in the cold. In fact, before the slew of unlocks hit, especially the GUI-based, anyone-can-use-no-terminal-commands-required anySIM, Apple's *stated* policy, I think Jowsiak (sp?) said it, was that as far native 3rd party apps, Apple would not support them but they would not intentionally break them; in other words, they would try to co-exist with hobbyists as best they could without going out of their way to keep native apps stable. As of London Tuesday, the obvious implied policy is: we will crush anything native. That sucks for you, since all you want is to put some different software on your iPhone, but you accepted the terms of the ATT exclusivity deal, you're in a contract, you pay your bills, you're harmless except perhaps to yourself when you brick your iPhone.
So, here's my suggestion: The iPhone hacker community, the native apps people, should band together and as a group take a formal stance against the unlockers. Go after them. It's the unlockers that have caused the sea change in policy toward potentially messy but otherwise harmless native apps. (In my opinion, it's the release of anySIM and it's more difficult to use precursors that have held up the current firmware update; from the looks of the fact Jobs leaked all the new features of the new firmware in Lond, he full well expected that firmware to be out by his London announcement, but then they had to backtrack to try and break grand scale, free unlock distribution.) The unlockers are your problem. Go after them. Shut them down and Apple no longer has cause to keep the iPhone so tightly locked up.
Apple CANNOT afford to stay ahead of the hackers. It took them awhile to hack it after it was released, but now that people have a handle on the phone, now that tools are available on the phone for hacking--basic programs like ssh, etc., it will take less than a week for a company with some money, or for that matter, a bunch of nerds with code.google.com, to workaround their stuff. Just wait for it on the ringtones. They'll have a new hack before next monday, and that's not even relevant--iToner, which doesn't cost all that much money, still works, so they haven't broken custom ringtones completely even with 7.4.2. And regular, honest users are going to start getting really, really annoyed with constant updates that do nothing but break hacks they aren't using.
If apple updated iTunes to brick your iPhone, someone would hack iTunes so that it didn't do that--e.g., denying it a network connection to phone home to apple to check out the phone. But that's not even the issue--that kind of crap is just BOLLOCKS to regular users who aren't hacking, or--users who are hacking (like me) but don't have their phones unlocked or anything... how will they tell the difference?