The only place the kernel actually uses configMINIMAL_STACK_SIZE is to dimension the size of the stack used by the idle task - and normally on the assumption the idle task is not doing anything much so doesn’t require much stack. The FreeRTOS standard demo and test tasks use multiples of configMINIMAL_STACK_SIZE so the same code is portable across many different architectures.
I recommend having stack overflow detection turned on while developing - then you are not left guessing as to what the issue is. I would also recommend using configASSERT(), especially on Cortex-M devices. You can read about how to do both of those things here https://www.freertos.org/FAQHelp.html