In terms of linkers, the state of the art has definitely been pushed in recent years (mold, the new linker from Apple, and the already mentioned gold linker) but some of these are so new that a book hasn't been written on it yet.
There's a PhD thesis I can't find on the topic that mentions some strategies for concurrent linking that came from gold, the big idea being that a lot of the work can be done in parallel and concurrently with the compiler generating object code (while the compiler is generating object code and before the final link step, scan the object files for their symbol definitions/requirements so the final link can be done very fast - iirc the idea came from gold).
In terms of loading, so few people work on these things and there's not a ton of interest in making it better that there isn't a ton of literature on the subject. The best source for the state of the art is the RTLD source in glibc and ld.so in musl, and equivalents in the BSD/Darwin/Linux kernels.
Loading is a lot "easier" than linking, and easy to make fast enough that I don't think a ton of research has been put into it. It's mostly determined by the executable format, and Linkers and Loaders is an excellent reference on their design. I also think that the people who work on this are doing it in environments that don't lend themselves to publishing papers and textbooks, but application notes and internal documentation at the companies that need to deal with the serious performance and security implications of a loader and executable format. And the executable formats have been proven to be very robust over the last few decades.
Language designers also take this for granted because they need ABI compatibility with system libraries to be useful, so most new language projects just reuse the linker/loader that is on the system instead of inventing a new one. And new projects have to be compatible with the executable formats created by existing toolchains, so you have a chicken/egg problem there.
i don't really know, but risc-v is important now, cheri is deployed as morello, pie for aslr and separation of code pages from read-only data are default, and aarch64 i think was brand new in 02008 if it existed at all. i'd guess c++ compilers have broken abi compatibility once or twice since then. oh also lto is a big deal now, enabled by llvm bitcode in many cases. also ubsan and asan didn't exist i think. not sure if those require linker support. also fuchsia and sel4 exist now and freertos is a lot more mature. so probably there is some new material that could be productively included
