Hello, Phillip
In theory it would be possible. I'm imagining that every loop and archive event would result in a RESTful push to the Davis site.
But, there are lots of speedbumps along the way. For example, the Vantage protocol is very stateful. Right now, weewx manages that state, but I can imagine that the Davis site would want to as well. Arbitrating that contention would be a challenge.
It sounds like WD gets around this problem by simply abandoning the console every once in a while and letting it communicate directly to the Davis site. I suppose weewx could do something similar, but it would not be, umm, "natural."
The lack of enthusiasm in the wview community may be because the Davis site uses a protocol better suited for a device driver than for a web application and its lack of elegance does not inspire anyone to give it a go. But, that's just my opinion.
In any case, give it a try. Weewx was designed for experimentation. This one may be a bit more of a challenge because it messes with the internal state machine in weewx, but it doesn't sound impossible.
-tk