The flexibility and quality you get by taking web "content" via json (rather than HTML) and rendering it natively is a huge win.
I don't see android customers paying for websites wrapped in an app anymore than I see iOS users paying for it, actually less.
Of course if you're making SaaS such as base camp then you can do native clients on either platform.... and sell them successfully... while selling a specialized web browser (That just gives you the base camp website in WebKit) wouldn't likely fly.
> "elite-ios-wiling-to-pay" customers are indifference about it
They are? Are you just throwing that out there or is there some research you can back that up with? In my experience, from watching users use hybrid applications (that is, native app shells around web content) they're perplexed about why things look "a little wrong" and the scrolling is "not as fast" as other apps.
Note: I design/develop Mac & iOS apps.
(OP as well)
It is not clear from your website what type of applications you have developed so far for iOS which make it hard to "judge" your choice whether or not you were right about choosing native over HTML5.
But I wish to remind us all that those two can, and in many cases should be combined.
If we take Google iPad suite or Twitter formal client, they are iOS apps which render content through the webkit object.
If your app deals with data which resides on the web, and with loads of it, perhaps rendering the presentation layer in HTML5 is not a bad choice as your "elite-ios-wiling-to-pay" customers are indifference about it, while at the same time, you can win the other market (Android).