That's sorta the idea behind server-rendered Blazor. Components are rendered on the server and passed over to the client via websockets.
Unsurprisingly, input lag and scalability can be major obstacles, but I expect it to make large headwinds in enterprise apps.
Of course I have yet to investigate how modern browsers render a never ending index.html, how I wouldnsend the client events and correspond them to the existing open original request, how this would scale to multiple hosts behind a load balacer (but maybe that’s getting ahead of my self haha).