As scarmig pointed it, the spec allows custom range units. Downloading pieces of a big file seems to be to be essentially the same problem as downloading parts of a long list of items.

Also, I'm imagining this header approach more for API calls than for bookmarkable user-facing pages. This way the data that comes back from the server can be a clean array of results without metadata. Feels like metadata is what HTTP headers are for.