Solution
Setting the minRate and maxRate properties to the same value for each message is the cause of this to happen. When using 100 kHz, it has enough timing resolution to meet the rate requirements, while at 13.3 kHz bitrate, the schedule builder can't satisfy those exact message rates and fails to build.
To correct the issue, add some slack to the message rate to allow the schedule to deploy with all Tx and Rx channles set to 13.3kHz. Setting the minRate and maxRate to +/- 1 of the desired rate is enought to allow it to deploy.