possible use cases of SEH w/ FreeRTOS have been presented here before, for example in Simple way to reduce code size when using FreeRTOS from C++ with exceptions enabled - Kernel - FreeRTOS Community Forums . Pragmatically, there is only one way to figure out if it works or not: Try…
As usual in engineering, it is imprtant to weigh costs against gain. In all customer scenarions I have come across, costs outweighed gain, but that is by no means always the case.
One thing I find particularly awkward to deal with when it comes to C++ native SEH (as outlined in the thread I linked) is that the run time system creates several memory sections without really telling you what they are and how to deal with them. Even if you have enough memory available, you will still need to consider them in your overall memory layout scheme (linker command file) to ensure that they do not interfere with your architecture (that can include subtle use cases such as where you temprorarily store images for a firmware update).
But again, it is up to you to decide whether it is worth a try. You publishing your results is very much appreciated by the community… 