Something I don't understand and which your use of the web control highlights:-
You seem to be trying to create a language with a small footprint. Is that right? If so, how does wrapping the web control up make anything smaller? You'll have all the same dependencies as a developer would if they just used the web control. And that's essentially the same as having IE on the machine. So what have you achieved?
The same applies to your language. At deployment you'll still have exactly the same dependencies as any developer using visual studio to develop VB6. They'll still have to ship exactly teh same components to their customer. Worse, you seem to be implying that they won't need to have the run time files resident on their development machine but that means they won't be able to run their own code to test it before they ship it.
You've called your tool an interpretter, which I can kind of understand. But all you're actually doing is providing an extra layer of abstraction between the developer and the code. And that extra layer has a footprint of its own. You're not making things smaller, you're making them bigger.
If you're aim is to make it easier to code by your extra abstraction then I can kind of understand where you're coming from. But I've seen enough bad practices in your code so that I wouldn't trust your abstraction as far as I could throw it.