Delphi – Compile Delphi component package (bpl) for different Delphi versions

Unfortunately, no. If the crash is due to missing imports from the .bpl files required by your application, there is no way (short of rewriting the Delphi RTL and linker themselves) to check for those packages from within the crashing executable itself. PatrickvL's solution is probably the best for your situation.

Neftalí's solution might be an option - of course, at the cost of packaging the RTL, duplicating a lot of files, and losing one of the points of having packages in the first place. However, if you're using private DLLs (i.e., if you copy the DLLs in your private binaries directory) then you should also create an empty file with the same name as your executable but appending the extension .local to it, i.e. for notepad.exe you'd create a notepad.exe.local. See Raymond Chen's article on DLL redirection for more details.

To get a list of loaded libraries including the complete paths you can run your application under the Dependency Walker, it will output a lot of important information.

You can also use it to show all static dependencies of various DLLs and BPLs, so you should be able to find the first module that forces BDERTL140.bpl to be loaded. You should try to load your patched version before that.