For yall the answer is yes as it is written by Paulo Moura who is very keen on portability. The SWI-Prolog version has some additional declarations to make the development tools cooperate better with it.
The redis package is more complicated. Several Prolog systems have emulated the SWI-Prolog foreign language interface. That makes porting parts fairly easy. Other parts depend on more unique features of SWI-Prolog though. Think of dicts (easy enough to implement for any Prolog system but it must be done in the core system), blobs that are used to encapsulate foreign resources in a safe way and provide garbage collection for them (also not that hard for any system than already has atoms with garbage collection) and threads (hard if you do not have them). In general the more modern libraries are harder to port as they more and more rely on SWI-Prolog features.
That is on the agenda to be resolved. How is still an open question. If anyone reads this who has the necessary skills or wants to learn them and is interested to play a role in this, please contact me. The whole thing depends on people, money and a plan Roughly I see three ways out. One is a big enough stakeholder to make this happen. Another is enough work for SWI-Prolog Solutions that allow hiring someone to take this role and the last is to bring a larger number of stakeholders together to establish paid support that is backed up either by hiring someone or a diverse network of community members capable of covering most areas. Other suggestions?