Posted 02 September 2013 - 05:40 AM
Interesting question! I think that the answer is probably "no", but I can see a few options for someone who wants to wrestle with the OpenVPN documentation. Here's some rambling thoughts..
Basically, for the purposes of this discussion, OpenVPN does two separate things; it
1. sets up an encrypted tunnel to the remote server, and
2. routes all traffic through the tunnel.
And the typical case is that one would want both.
Now, I'm no expert at using OpenVPN, but there seems to be enough things to poke at that an Air customer could relatively* easily have it do  above, but not . At that point, I think, you would have access to Air's network, but no traffic would use the tunnel - unless it were actually addressed to somewhere in Air's internal network (like for example their name servers or the speed test thing).
If Air were to run an HTTP (web) proxy (and they don't, as far as I know), then what you want should at this point be as easy as adding that proxy to your browser just like any other. Traffic going to the proxy would be routed through the tunnel since it would be explicitly going to an Air address. (10.x.x.x)
But since they don't, you would probably have to at least run a custom HTTP proxy on your machine that would forward traffic in the right direction, and I'm not even sure how that would work. It's not completely beyond the realm of possibility though, networking seems to have an almost infinite amount of weird solutions to even weirder problems.
And of course I have no idea if Air would even want to support people doing things like this.
* "Relatively easily" would still involve getting intimately familiar with both OpenVPN and Air's network and writing a custom config file, at the minimum.