Teensy 3.5/3.6 pin assignment status

Hello,

I am in the process of designing a 3D printer board that is driven by the Teensy 3.5/3.6 micro controller. I would like to make sure it is compatible with Marlin. In reviewing the current pin map (https://github.com/MarlinFirmware/Marlin/blob/bugfix-2.0.x/Marlin/src/pins/pins_TEENSY35_36.h), I have the following questions:

1) Is this pin mapping set in stone?
2) Is it intentional that the diagram and the actual pin definitions don't match?
3) Are there boards released or being developed that use it?

I have some thoughts and suggestions, but I don't want to break anyone elses work. My project is fairly maleable at this point but I'd like to make sure some of the communication peripherals are not blocked. If the current set-up is locked, I'll just make my own board type for Marlin once my board is complete.

Thanks,

Phillip

You make your own pins_{your_board_name_here}.h to suite your board

Then you dont break what ever they are working on with pins_TEENSY35_36.h

Quote
Dust
You make your own pins_{your_board_name_here}.h to suite your board

Then you dont break what ever they are working on with pins_TEENSY35_36.h

That is reasonable. I wanted to avoid unneeded board additions, but making my own pin definition is probably the best way to avoid conflicts. Thanks.