HTML 5.0 draft (before W3C got into their stupid versioning) contained some of your request already.
1-2) ISO date format needs to be forced upon everybody. like the metric system. However, the spec doesn't require the browser display with it. Browsers are free to display the date in a localized format while submitting the proper ISO format. This wouldn't be much different than how Options display different values. Perhaps the spec should mention this so nobody fears doing this...
3) HTML5 is good enough already; doubt you'll get them going further anytime soon. I can imagine from my experience with them that is how it'll go. I agree with you that it would be convenient.
5) Initially, integer didn't suggest a incremental button (that I recall) but later the spec showed an example. The problem with presenting suggestions or screenshots of implementations is that every literal minded developer will copy it. The CSS groups are slow as hell and not in sync with HTML5 like it should be; could be how they create lots of tiny CSS working groups with narrow focuses and that doesn't respond to HTML5's requirements well enough yet. HTML5 tries to define appearances in CSS but that becomes a chicken/egg problem. Turning on the incremental buttons needs to be CSS... a slider presentation would also make sense (there is a big bias towards minimalism. Yet METER is creating quite the CSS challenge for them... which will be much more complex if they just begin to address all the requests out there for it.)
6) Would be nice; however almost everything has either 2 decimals or 0. Just a few have 3. So an integer with step=0.01 would work well enough. Don't expect that to happen. Currency conversion or selection won't happen; that is too complex - you implement it. It would need to know what currencies you support so then you are somehow using a bunch of option tags or creating some odd list attribute.
7) Country selector would also be nice. possible issues are related to constantly changing flags and countries in less stable places. If you implement it then you are in charge of handling those situations. You can do a Select with country flags already before HTML5.
8) Credit cards - update related issues long term. similar issues as country listings but worse. Perhaps you can gain traction with the working group if you team up with a browser and aim towards CHIP and RFID support --- maybe we could finally get an encryption input !! It's not a new issue and they never handled the 2-way communication that is involved with an encryption input. (nobody even touches the cert authentication features in the browsers already except http://startssl.com/
9) HTML5. has it. no validation possible. But it SHOULD use the proper keypad on a phone. I investigated this; it's crazy to go global with it which is why it was left open. Implementing is way too much work. With VOIP it seems that it would be pointless long term because any kind of phone number could be used anywhere; restricting this will become an issue in addition to keeping up with global changes in format. The only standard is the international prefix... except I found a few places where that didn't even apply within their country.
10) HTML5 did it already. Has the best RegEx for email too- it's in the spec. check it out!
11) HTML5 doesn't handle editors; however W3C is trying to standardize kludges. the groundwork on roles helps slightly but yes, it's all kludges. There are so many options on this one that it is highly unlikely to standardize. They really don't like taking something with a million options and standardizing on 1 simple solution.
12-14) Yes, that would be nice. However they have added groundwork to make that much easier for you to do in HTML5. drag-n-drop files; local file access; AJAX file upload. The old "accept" attribute does work even though it's use is optional.
15) never. same as 11. but 11, 12-14 related features make it easier to implement (because they are not specific but general features that make it easier to roll your own.)
There are plenty of open source kludge solutions to choose from; that also is why you won't get much traction. Best bet is to get a browser to implement something non-standard and use that to push change. Too often there is a situation where each side is waiting for the other one to start something. For example, try to get multiple select to have checkboxes instead of the bad UI idiocy we've had for decades (most users don't know they can select multiple unless you tell them and many don't know the keyboard shortcuts which differ by platform) it is impossible - a bug report on bugzilla which dies because HTML5 doesn't have it while HTML5 won't touch the issue until a browser does. That is just fixing bad UI on a common use case already recognized by specs back to html 4.