> that loose back-and-forth over HTTP weighs more than an always-open WebSocket

This is definitely true for HTTP/0 and /1. Is it still true under HTTP/3, or has the underlying ‘single conduit, many channels’ model improved things if used correctly?