I have done a fair bit with re-ordering the returns from a FTSearch or a viewEntryCollection. A getAllEntriesByKey returns the viewEntryCollection in the same order as in the view. When that does not do it then my next would be a documentCollection or a FTSearch and then pass the resulting collection into a TreeMap to get the documents in the correct order. The process is actually pretty fast and the sort order etc can be controlled very precisely. A little bit of code, but that's the way that I would do it. I did a test on a returned collection of 5000 documents that I did the treeMap and returned it to a repeat control and the response was fully acceptable. I always run my test on an old server that is memory and processor challenged if it works well there then I know that when it gets to a production environment it should perform well.
I went down the @DBLookup road for awhile before frustration and kludge said that I was going down the wrong road. Backed up and built the treeMap process and wont go back. I believe David L has a video on treeMap and hashMap on his Notesin9 site take a look at that. As I said it took a bit of time to get the treeMap working but well worth the trouble IMHO.