That sounds really unnecessary and just added complexity to me. If you the dev of an application you already know of all it’s dependencies. From a debugging standpoint this doesn’t make any difference. You pop the application in gdb replicate the steps that cause it to fail or produce the undesired behavior and gdb will give you a stack trace of where this code crashed/you stopped it. Including full path and line number of the libraries the code is coming from.
From a consumer stand point also this doesn’t seem to produce any significant benefits? Almost no consumer is going around trying to locate the libraries used by the application and on the offchance they do we can use pactree here (debian has dpkg equivalent flags for this and pretty sure so do redhat distributions) to list all the dependencies of a package and ldd to print the specific .so libs being used by a elf file.