Indeed, WebClient
functions as an HTTP client rather than a web browser.
An HTTP client abides by the HTTP protocol; therefore, the content of your HTTP requests being HTML is inconsequential to the client.
In contrast, a web browser possesses the ability to interpret HTML responses (along with executing JavaScript and more) in addition to serving as an HTTP client.
If you are seeking a tool that can load HTML and run JavaScript on the DOM without rendering like a traditional browser, you may want to explore "headless browsers". These headless browsers are often faster due to their lack of rendering processes.
Various headless browsers exist, such as HtmlUnit (with potential to be converted for .NET usage) and envjs (JavaScript-based, suitable for embedding within .NET). Although I have no personal experience with these, they appear quite promising, especially envjs. Update: a comprehensive list of up-to-date headless browsers has been shared on GitHub.
You may also want to explore other alternatives to the WebBrowser
control, which could potentially offer improved performance while remaining within a controlled environment.