Background processes, cross-domain AJAX and file I/O actually are possible now, at least to certain extents. It's getting a lot better, but as you say, Apple drag their feet at every opportunity.
Also, HTML5 location tracking is severely broken on iOS. In most cases the user ends up inadvertently blocking permissions for Safari rather than on a per-website basis. The result then is that all future websites get blocked from location access automatically, without even prompting the user.
If HTML5 apps are to take off, the web browser needs to be treated as a basic component of the OS and automatically given full access to location tracking and sensors; it should then be the web browsers' responsibility to ask and confirm with each website and manage those permissions (perhaps even seamlessly integrated with the OS permission system itself).
IMHO the restrictions on HTML5 apps like cross-domain requests and iframes are quite silly. At least there should be a one-click way to "trust" websites in the same way you'd install an app.
Unfortunately mobile web pages can't run background processes, can't launch AJAX requests to arbitrary domains, speak UDP, do file I/O, and numerous other things, which is why people end up writing apps.
Also mobile web browsers still suck, unfortunately. Safari still hasn't gotten its act together with simple stings like scrolling, and is riddled with CSS bugs of sorts if you try to do anything advanced with HTML5 (e.g. pull to refresh, swipe gestures). It's almost like Apple is deliberately refusing.