If you put a file or a link in the dwarf fortress "libs" folder, DF will find those first. This may less risky than other options. I do not know if LNP also has a libs folder as a pathing prefix for library lookups. In my /df_linux/libs/ folder, I have these links:
[size=8pt][size=10pt][font=courier]lrwxrwxrwx 1 b 45 Sep 18 10:33 libSDL_ttf-2.0.so.0 -> /usr/lib/x86_64-linux-gnu/libSDL_ttf-2.0.so.0
lrwxrwxrwx 1 b 45 Sep 18 10:39 libSDL_ttf-2.0.so -> /usr/lib/x86_64-linux-gnu/libSDL_ttf-2.0.so.0
lrwxrwxrwx 1 b 45 Sep 18 10:39 libSDL_ttf-2.0 -> /usr/lib/x86_64-linux-gnu/libSDL_ttf-2.0.so.0[/font][/size][/size]
I added those so it would find the right libSDL_ttf file, but I cannot recall now if I had to install a package to get that "/usr/lib/x86_64-linux-gnu/libSDL_ttf-2.0.so.0" file on my system. I am no expert with Linux, so your mileage may vary.
I don't know anything about getting LNP running, but you should be able to use the "ldd" command in the same way, like "ldd LNP", to find out what the LNP app is missing for packages, then do the same for DFHack. You do need to use "ldd" on the main binary, not on the shell script typically used to load the main binary. You can text-edit the ./df file and see it calls the ./libs/DwarfFortress file, which is the reason I gave the commands to run ldd against the DwarfFortress binary...., LNP might have a similar setup of a shell and a main binary, or it might just use a script to set the environment and then call DFHack). It is likely that if you tackle the problem this way that you'll find what you need.