Hi,
The regular OpenOCD GUI is indeed optimized for running OpenOCD locally – it can automatically find the supported JTAG/SWD probes, install drivers, locate device scripts, etc.
If you would like to run OpenOCD remotely, please try selecting the “Full-custom” debug method instead of OpenOCD. It allows specifying arbitrary target connection commands, and will not attempt to do anything beyond what is explicitly configured.