This is not a FreeRTOS limitation; it is a consequence of how the port and the surrounding SDK are implemented. However, it does reduce some of the flexibility normally associated with FreeRTOS, particularly in light of discussions such as How to create Semaphores (/kernel objects) before Scheduler start and Using FreeRTOS primitives before starting scheduler, where creating RTOS objects prior to starting the scheduler is presented as a supported use case.
My goal was simply to get an expert opinion on whether this type of critical-section mapping is considered a sound port design. In practice, it appears to force users to move initialization into a dedicated startup task and allocate resources for that task, even in cases where the RTOS itself or application design do not require such an approach.