So, there is good news and bad news.

The good is that I was able to link a project that references a WebCore::Page and implements quite a bit of WebKit interfaces (even if they're mostly placeholders).

The bad news, is that the resulting binary is already over 80MB, meaning memory requirements of the new browser will likely be ~1GB. Mind that the binary doesn't actually do much past instantiating a WebCore::Page, so it's bound to grow a lot by the time it starts resembling something usable.

Next step: figure out the minimal route to load & display contents, the dumbest way possible, just to verify that the WebCore internals are working.