Does that approach really work for a 72GB dataset? I assume that means DuckDB will need to load all that data in the browser?

Client side it is aggregations of the data, (so yes you could run out of memory). DuckDB does not load all of the data client side.

I'm not sure if that's exactly what you mean, but I've used http://brace.io/ in the past and I found it pretty good.