DLLs will still work so long as the authors used basic update-proofing measures like sigscanning. The only thing that can break them is changing the functions they use so the scan fails, or modifying hooked functions such that the arguments are different or new control flow breaks them, which is unlikely with these changes.
DLL loaders will break if they use something like modifying the imports table to load a bootstrap DLL. This is easily fixable with a tool that can change the PE header, though.
It might be time to reevaluate where DLL modifications are going before the existing problems keep multiplying. Many are made naively and should follow some rules, i.e proper function hooking to maintain compatibility, linking against Blockland's runtime instead of having a billion different ones because authors use whatever visual studio they have (also breaking wine support), more control over when loading and unloading happens, etc.