HTTP2 and avoid unnecessary requests response cycles

Does it still makes sense to “club multiple requests into one” in an HTTP2 world? Given that HTTP2 can handle multiplexing and reuse of a connection, could multiple smaller requests be a performance improvement?

I don’t mean to purposely split up a single request but rather to refrain from combining just to reduce requests. The added benefit of multiple requests is a more efficient caching strategy - combining multiple requests needs a strategy that works for all, which likely involves less aggressive caching of at least one resource than we would like.