It seems like the query planner could perform this optimization, but also it seems like the index could maintain cardinality data to avoid requiring a scan/offset of ids.

If the index had cardinality metadata, it could jump directly to the leaf node containing the first row in the result set.