You don't like closed systems? Fine, but calling those systems "Harvard" architecture(s) is kind of misleading.
In Microchip PIC land, that would be especially inconvenient, because of the different data vs. instruction size.
I'm not complaining about desire for control at all. I'm complaining about the inability for a program to treat it's code and data as the same medium.
That is very much the key tenet of a Von Neumann architecture.
You might as well argue that Linux isn't really a Von Neumann architecture because you can only execute files that have the executable bit set.
The concepts that I would categorize as the von Neumann architecture are incredibly basic. Equating his plan for computer design with a difference between storing program/data vs. just program misses the mark. Von Neumann wasn't at all concerned with this difference.
Take this quote from "The Computer and the Brain": "Large digital machines are made up of 'active' organs and of organs serving memory functions-I will include among the latter the 'input' and 'output' organs.."
You can see how basic his thinking is by today's standards, and why Dijkstra later criticized him, and other American computer scientists for anthropomorphizing machines. He talks about 'an organ serving a memory function', he doesn't even talk about main memory because that word isn't in use yet.
You're interpreting von Neumann from a modern context. You don't understand just how basic and fundamental his ideas were.
Also, digital watches of all sorts have pretty much always been Harvard architecture for the past N years. From a use case perspective, the iWatch should be treated as a glorified digital watch, not a minified iPhone. Seen from this angle, I disagree that the iWatch is a "step backward". But I do agree with you that in general, Apple is annoying for deliberately limiting freedom.
As far as the iwatch being just a watch, the same thing could have said of the iphone. It was a phone, only cooler. Almost a decade later, ios devices are the platforms where many users do a significant fraction of their computing. And while ios devices may not require on bitcode submission, they limit the users freedom in a way that is fundamental. Image a world were every x86 computer sold post 1995 (outside of the server space) could only run Windows.
Besides, even if you own a "creation machine", you'll often be catering to the market of restricted devices (case and point: gecko on ios).
EDIT: I'll grant you may be right in the specific sector of non-computing electronics (watches, calculators, etc).
The reasons for Apple, Microsoft, and other vendors for restricting execution of native code are various, but mostly related to security and maintaining control of the ecosystem.
It is fine to complain about that desire for control. But it is not necessary to view this as a computer architecture issue at another level.