According to NI
Performing a Batch re-save will correct the file paths of the samples for all KONTAKT Instruments within a Library.
There is no mention of it otherwise altering your libraries.
From my experience in the past, before I knew of Batch Re-save, I found that adding library paths to Kontakt's database usually resolved file missing errors. Assuming my recollection is accurate - that would indicate that if Kontact can't find a sample that it searches it's database; therefore having the correct path in the library would speed up loading.
FWIW here's an article from NI:
How Can I Optimize the Performance of KONTAKT 5? My issues with Kontact performance...
I have 24gig of RAM but it does not feel like Kontact is taking advantage of it.
With some MIDI tracks and some libraries the voice stealing is really obvious when there is ample RAM still available.
I end up having to split the MIDI between tracks and use different instances of Kontact.
In regards to Kontact's database - Kontact mentions that having a high number of items in database will increase the memory footprint of Kontact and reduce the available memory for instruments.
No mention in NI's opimization guide about that. I am wondering if pruning the database would improve things.
TBH I'm not sure what function the database even serves if all your samples are correctly mapped.