Emanuelle's version ran at 115,200 baud. AR488 also runs at 115,200 baud by default. The baud rate is not that critical so long as the baud rate configured in the connecting software matches that of the adapter. I believe that the default baud rate for KE5FX is also 115,200 baud although this can be set to an alternative value in CONNECT.INI.
In order for KE5FX to recognize the interface, it must have a specific character sequence in the string returned by the ++ver command. The same is true for EZGPIB.
KE5FX requires the sequence 'Version 6' and is case insensitive.
EZGPIB requires 'GPIB-USB'
The fixed character sequence returned by Emanuelle's program when using the ++ver command is:
ARDUINO GPIB firmware by E. Girlando Version 6.1
On the AR488 the version string displayed with the ++ver can be set to anything convenient by using the following example commands:
++id verstr AR488 GPIB-USB version 6
++savecfg
This will set the version string to 'AR488 GPIB-USB version 6' and should be enough to get the interface recognized by the Prologix GPIB Configurator program in KE5FX Tools. The version number does not actually require the '.1' suffix, but there is no harm leaving it in if preferred as per Emanuelle's version string. The second command saves the setting to EEPROM. This is important since we need the version string setting to survive a reset. That the string has been saved can be confirmed by resetting or power cycling the adapter and using the command:
++id verstr
This should display the string entered in the previous command.
That PB variant of the 328 seems to be a bit of an oddity as it is not supported as a processor for the Nano in Arduino IDE 1.8.19 or 2.0.1, both of which support, as you have noted 328P and 328P (Old bootloader), as well as the 168. No listing of the PB variant in either IDE. The PB variant appears to be almost the same as the 328P but there are some minor differences including fuse values. Not having come across one of these myself, I am not sure how to deal with it yet, but I am happy to purchase a couple to experiment with if someone could point me in the right direction.
Incidentally, all these chips have EEPROM. The 32u4 has 512 bytes, the 328P and the 328PB both have 1024 bytes. Non-AVR boards may not have EEPROM. Examples include the ESP8266 and ESP32. However, the Arduino framework for both of these boards supports an EEPROM library that implements EEPROM in flash.