The current implementation of readLock=change is a bit slow as it does a change check per individual file one by one. What would be better to speedup would be a holistic pass on all the files and then detect when files are no longer changed faster.
A caveat is that if you must poll the files in a specific order then the first file must be ready before the 2nd etc and therefore this faster approach does not work for everybody.
Such a functionality is currently not in Apache Camel. As a Fuse customer you can use the Red Hat Customer Portal to log a Enhancement request to have this in the roadmap list for the product.
An alternative is to build your own custom read lock implementation that works faster using the approach I discussed above.