Should we add a "slow range query" to xxxPoint classes?

Users that index 2D point data have the option of running a range query with, 1) the points index (via LongPoint#newRangeQuery), or 2) a doc values field (via SortedNumericDocValuesField#newSlowRangeQuery). But if users are indexing points data in higher dimensions, there's no equivalent "slow" query that I'm aware of (relying on doc values). It's useful to have both and be able to wrap them in IndexOrDocValuesQuery.

I wonder if we should model a "point" doc value type (could just extend from BinaryDocValuesField) that supports creating "slow" range queries?