You wouldn't only need a js engine, but also a DOM that could be updated by the js, plus a CSS engine that would match your css rules against your dynamic DOM so it can find out if it has to download some other resources such as images, fonts... In one word: a browser.
Up until now, every tentative I'm aware of to do load testing with browsers, even headless, were failures: too CPU and memory expensive, even when massively scaling out with a cloud host solution.
Regarding the rise of js frameworks, the trend is to have some js client calling some REST APIs, ie plain easily testable JSON payloads and logicless server APIs. What you want to load test is the server APIs, and Gatling does a good job for this.