Handle hardcoded paths in binary-only drivers / libraries?

What’s the best practice to handle hardcoded paths in proprietary/binary-only drivers or libraries? I want to use and package the proprietary SANE-scanner-drivers for Fujitsu / Ricoh SP-series document scanners (e.g. SP-1120, SP-1125, SP-1130), so I (and others) can use the scanners on NixOS. Fujitsu/Ricoh only provide a binary-only driver for Ubuntu. The libraries of this driver contain several hardcoded paths: /etc/sane.d/ /opt/pfusp/ /usr/bin/ps /usr/bin/grep Since the driver does not fin...