The architecture of the PiDP products allows the front panel driver code (server) to run on a different system from the actual emulator (client). Of course, the client is trying to drive the front panel as a real-time device and network latency or other delays may cause the front panel to be less responsive than running the client on the same system as the server.
Given that a Raspberry Pi 5 is quite a few times faster than an actual PDP-10 and you need a Pi inside the case anyway, most people don't bother with running the emulator on different hardware and that code path has only been lightly tested, if at all. Working on the PiDP-11, I've found several things that are broken when they are running on different hardware. I don't know if the same is true on the PiDP-10.
You should probably use Debian Bookworm on your laptop if you decide to proceed with this. You may find that either the install or operation of the PiDP software doesn't work the first time - going by the PiDP-11 code, there are quite a few assumptions that packages will already be present on a default OS install. While the Pi uses Debian Bookworm, it has had quite a few additional packages added to the standard Raspberry Pi OS distribution that aren't present on a vanilla Debian install.
As far as terminal emulators, if they work when the client and server are on the same system, they should continue to work when the client and server are on different systems. The terminal emulators basically do either a "screen -d -r" or a "telnet localhost <some-port-number>" and they are doing that to communicate with the emulator running on the same host.