There is nothing planned in v5, v6 would be the next opportunity, I guess that will be after 2020.
Really though, the way to solve this type of issue would be to have all the data (symbol, footprint, 3d model) in one file. For as long as there is a file path embedded in a file, the possibility of getting out of synch is likely. I guess an alternative is to have fine grain versioning of objects, but that is also a whole lot of work. A simpler option more in line with current KiCad might be to have 3d library tables, and use a "lib_name:model_name" identifier. Oooh, and then add versions "libname:object:version", that could also apply to footprints and symbols
Well, designing on paper is easy, in the meantime, we'll have to rely on everyone understanding the library workflow.