Also using printf family logging functions in ISRs might be a problem.
They usually need quite a lot of stack (main stack in case of Cortex-M CPUs like your Cortex-M7) and often are not safe to be used in ISRs).
I’d just omit that in the ISRs.
In this regard stack checking for tasks is useful to verify that you provided enough stack even when using logging.
I think with your FreeRTOS version configASSERT would catch wrongly configured interrupt priorities. But it seems you’re using cube to generate parts of your code this might be configured correctly..