It is allegedly faster to load the libraries as a single large file than from folders full of folders full of individual objects. But I must say in my informal testing I haven't observed a dramatic difference among loading library folders, PLAs, and LCFs.
In addition, there's at least one characteristic of LCFs (and archives) that is disadvantageous. You can't save objects into them. So no new objects and no editing. (You could view this as an advantage from a standards point of view; nobody can mess anything up.)
In other words I considered using an LCF for the Rill & Decker Standard LIB but decided against it. There's no change in everyday library management.
But! There's a huge advantage to the LCF in one specific case: Copying libraries to a flash drive to take them home. The R&D library is about 15MB. Copying its 1300 or so items to a USB 2.0 drive takes over two minutes. Copying the same library as a 15MB LCF takes, drum roll, three seconds.
It also takes the guesswork or other syncing strategies out of keeping your home copy of the library up to date. Just bring the LCF home and overwrite the old file.
So I'm providing the library as an LCF for this purpose. The file lives at 2 Libraries / Library Container Files. I will do my best to update it when anything important changes. This is pretty often, so make sure you check it regularly.
You still need to manage project libraries manually.