I will say that I have never been able to brick an MIMXRT by a failed or corrupt program operation. However, I have observed something like this happen in the case where I load code which does something bad in the startup phase (e.g. where the first few assembly instructions set an invalid FlexRAM configuration or read from a peripheral which is powered off). When this happens, the debugger isn't able to connect to the chip, because the chip starts executing the first lines of code *after* being reset by the debugger but *before* the debugger can pause it, and then locks up.
To recover from this type of situation, you have to use the boot mode pins to start the MIMXRT in another boot mode, such as Serial Downloader. Then you should be able to connect to it again in the debugger as it won't execute the bad instructions out of flash. Hope that helps!