Yes, it is possible the environment version is different on GCC. I would almost assume that based on what you are seeing vs what I'm seeing.
As for the collections - It's quite misleading...almost everyone has been conditioned to use collections for everything from a single value to millions of records. They are overused and have an overhead to them.
They have their use and purpose, but when they are not needed, they should be avoided.
In your case, you are using a collection to try and grab all the data into your app. Here is where things are misleading, you only hit the REAL datasource once in your app. That is when it loads the app (or, depending on the advanced options - when called for). What does that do? It actually collects information into a session table in the cloud service. Once you call for a bit of data, the cloud session either has it already in the session table and returns it, or goes and grabs it. THEN, and here is the part to consider, when you use that bit of data again, it is already in your app as you called for it before. It doesn't go back to the datasource to get it and in many cases (depending on your advanced settings) it doesn't even go to the cloud session table...doesn't need to, you already have it.
So...if you have, let's say, 1000 records in your datasource, and you LookUp record 500, you will get that back. If you LookUp record 500 again, you will get that again, without the trip to the session table. If you LookUp record 100, again the process is the same. If you Collect all the records and then try to push that into another collection (which is a common practice for gathering large sources) causes the session table to have to be accessed for all 1000 records. This is in many cases a lot of time.
Again now, going at your case, you are dealing with a Document Library. There are a lot of delegation traps in Doc Libraries because there are a lot of "generated" columns.
My recommendation is to resolve delegation issues at the onset of the app to make sure your datasource is going to have the ability to delegate. This is easily achieved. And, once you have it, you don't need to worry over the large amounts of data for filtering non delegable criteria. Because, if the criteria is delegable, then the session manager will be able to pass an odata query and return a session table for that.
Now...(sorry to rattle on a bit), if you HAVE to have over 2000 records in your app for a display purpose (which I would say one should reevaluate the need for that) then a collection is the only option.
Collections are only needed in cases where you need to store and manipulate over the record limit of the app records, or where you need the ability to add or remove rows in an "internal table".
So, bottom line, resolve the delegation issues and make sure your app never NEEDS over 2000 records at a time and things will not only perform better, but also reduce the chance of overrunning the app memory.
What does all of this have to do with your original issue? Nothing, but I guess I opened that can of worms...and it was fun to write.
I hope it is helpful in your designs.
@stephenJames