Yes, you could.  However, that is a very resource intensive process, and general control systems lack the unique features that cmdBridge offers to make things easier to configure and deploy.

Key differences between using a standard control system and cmdBridge are below;

cmdBridge is cheaper than all but the most simplistic control system.

Staff qualified in the control system, licences, and development environment are not required.

Rapid deployment, for example, an engineer can be told to use spare projector 3, grab a pre-configured cmdBridge, set the physical interface parameters and activate stored translation 5.  All of which takes a couple of minutes and no need for a programmer to attend.

cmdBridge has multiple power sources available.  Just plugging it into a computer to configure it will power it.  No additional power supplies are required.

An integral dual port 10/100 ethernet switch makes deployment easier.

You can change the MAC address of cmdBridge to match the faulty equipment, so no network changes are required for deployment.

Capture mode will snapshot a working system, creating half of a translation file automatically just as fast as you can operate the system.  The data is de-duplicated, too, with the context-sensitive nature of the command reply structure maintained.

cmdBridge can hold up to 32 translation files internally for rapid deployment.  Select the translation, configure the source, target physical interface, and cmdBridge is ready.

cmdBridge boots in seconds.  By the time you have finished reading this, it will have booted up and be ready to go.  To be of use, a translator must boot up before the control system starts to send commands.

cmdBridge translations are physical interface agnostic.  Therefore, whether the physical interfaces are different or operate at different speeds doesn't matter.

Sorry to say it, but the best answer is for you to read the cmdBridge reference manual. The full syntax of the command translation file is at the end, along with an example.

To give you a sneak peak ahead of you reading the manual, here is a small configuration file example.

desc = “EPSON EB-535W to NEX NP-M302WA (mute example)”; 
var mute = 0; 
command { 
    desc = “Set Mute ON”; 
    source_cmd = “4D 55 54 45 20 4F 4E 0D”; 
    target_cmd = “02 10 00 00 00 12”; 
    reply { 
        desc = “Reply Mute ON OK”; 
        target_reply = “22 10 01 20 00 53”; 
        source_reply = “3a”; 
        set mute = 1; 
        } 
    } 
command { 
    desc = “Set Mute OFF”; 
    source_cmd = “4D 55 54 45 20 4F 46 46 0D”; 
    target_cmd = “02 11 00 00 00 13”; 
    reply { 
        desc = “Reply Mute OFF OK”; 
        target_reply = “22 11 01 20 00 54”; 
        source_reply = “3a”; 
        set mute = 0; 
        }
    } 
command { 
    desc = “Get Mute status”; 
    source_cmd = “4d 55 54 45 3f 0D”; 
    reply { 
        desc = “Variable based reply, off”; 
        source_reply = “4d 55 54 45 3d 4f 46 46 3a”; 
        flag = conditional; 
        if (mute == 0); 
        } 
    reply { 
        desc = “Variable based reply, on”; 
        source_reply = “4d 55 54 45 3d 4f 4e 3a”; 
        flag = conditional; 
        if (mute == 1); 
        }
    } 
end 

The good news, you do not need special software to edit configuration files.  The file itself is just plain text, so even something like Notepad can be used to edit a file.

If you use the capture mode in a working system, cmdBridge will generate a template file for you.  This will be pre-populated with the commands and replies from the live system.

However, be careful of some editors trying to be helpful, specifically by changing the " marks into snazzy open an closing quote marks.  This will be a sure way to get a syntax error when uploading a config file.

No, it isn't.  Whilst the console port is USB, it appears to your computer as a serial port.  So you need to ensure you have the correct settings for everything to work as it should.

The settings you are looking for are 230400 baud, 8 bits, no parity. 

Not very long at all.  By the time you have read this answer cmdBridge will have booted, read any stored translation file, setup the interfaces, and be ready to go.

If the equipment being replaced uses a DHCP assigned IP address, you can clone the MAC address of the faulty equipment onto cmdBridge.  If the replacement equipment is also IP, set the loan equipment to a new IP address and plug it into one of the two ethernet ports.  Give cmdBridge the IP address of the loan equipment and you're good to go.

No need to get a local IT team to update their DHCP server.