You're just all over the place aren't you, 3-4 compilers, 2-3 devlopement systems, different IDEs, different bootloaders - it must be confusing. It is for me, trying to follow along what you're trying to acomplish....

The Firewing board is a PIC18F46K22 loaded with a "special" (ie not MicroCodeLoader) bootloader.
The AMICUS18 board is a PIC18F25K20 loaded with another "special" (ie not MicroCodeLoader) bootloader.

The Firewing development board is supported by the free Firewing compiler, just like the AMICUS18 is supported by the free version of the Proton compiler but at the end of the day they are both just a PIC on a PCB and the PBP compiler supports both of those PICs + hundreds of others.

The "problem" with both the AMICUS18 and Firwing development board is that their respective DRIVER (ie what needs to be installed on the PC) are custom tailored to the specific board (ie, when you plug it in it shows up as an AMICUS18 or a Firewing Communication port (despite it being just Another COM-port)) in the device manager of the PC. This allows the their specific bootloader application on the PC (ie not MicrCodeLoader) to find the board without knowing which COM-port it is but it also means that A) it won't work on Windows 10 (becasue the device driver is not signed and Windows 10 refuses to load it) and B) it won't easily allow you to load ANOTHER, generic, bootloader (like the MicroCodeLoader) into the PIC without first messing about with FTDI chip on the board, changing its settings so the board presents itself as a normal COM-port.

1) Choose a PIC that can do what you need
2) Choose a compiler that can generate code for the desired PIC
2) Choose an IDE that integrates with the compiler (or don't, it's not strictly NEEDED).
4) Then, optionally, choose a bootloader that works with the PIC you're targeting.

Don't try to do it all at once.

/Henrik.