If trie fields are indexed in parts, NumericRangeQuery will produce invalid results for multiValued fields... that's a limitation of the trie encoding (not easily fixable at all).
I do not really understand the problem with MultiValueFields. I had trie fields in my index in the past that had multiple trie values and numeric range queries worked with it. What is the problem? You should be able to add more than one value using separate Field instances to the index.
A NumericRangeQuery on a MultiValued field should show results for all documents as soon as one of the indexed values fall into the range. Correct me if I am wrong!