OK, so what are you trying to configure the ports as? Perhaps "configure" is the wrong word. Configure to me means set up the protocol so the two devices can talk. I would believe that since it is a MNEA multiplexer the only language/protocol it might speak is MNEA 0183. Not at all sure how you could possibly change that.
In any case your "9 pin USB cable" is going to be problematical as USB only has 4 wires and the USB ports on a MS OS are not seen as "serial comm ports" (which is totally dumb but that is how MS does it).
So using hyperterminal with USB is not going to work unless you know the USB port memory address on your computer (start-settings-control panel-device manager?)
Just getting a USB to serial cable will still require you to map hyperterminals comm port to the USB port memory locations.
Another way of saying this is hyperterminal has a pull down menu where you select the comm port you are going to use. Since you do not have a serial (mini D) port you probably just get a blank pull down. If you did have a mini D serial port it would be COMM (1.2,3, or 4) and that would still not be a USB port.
If memory serves hyperterminal has a set up page where you can specify the ports and memory ranges to them for "odd user configurations". If you can ID the USB port name and memory range and the actual protocol (for NMEA in this case) you could enter it there and it will show up in the pull down as a valid port.
I have no idea if this will work as MS has taken upon itself to "defining USB" as something less than Universal and I don't even know if it will operate at "reduced baud setting" or "other than 'universal' port settings.
My advice is to just forget the USB to serial cable and go serial to serial
or
Use Linux where you can just plug it in and it works automagically with the terminal program. Ports is ports in linux.