ST-LINK (the hardware, at least) actually works fine for programming/debugging other vendors' ARM-M series ICs- used it a lot in the past for Nordic's nRF52 series. I was using OpenOCD, not the ST-LINK SW, though, and have never tried on a Cortex M7.
First thing is to triple-check connections- that you don't have wires plugged in off-by-1 in a connector. Also that everything is actually getting power (and what voltage it's using- 1.8V, 3.3V, etc.). I don't know where you got that pinout, but making sure it's correct wouldn't hurt.
It's been a while, but IIRC some ST-LINK models require you to have a target voltage reference connected- that may well be what the "???" pin is. It may help to probe that pin and figure out what it is and post exactly which ST-LINK you're using- official ST-LINK V2, some knockoff, the ST-LINK built into an STM32-Discovery board, etc. Again, it's been a while, but IIRC some of them have limitations I don't remember off the top of my head- might be they only worked at 3.3V and we were using 1.8V systems? My recollection is that the official ST-LINK V2 (not the isolated model, not the mini model) is the "good" one that works with everything.
You can also try reducing your SWD frequency to see if that helps, but I wouldn't be super optimistic.
Finally, I see in the MIMXRT1052CVL5B datasheet "Support for 5-pin (JTAG) and SWD debug interfaces selected by eFuse". I didn't probe further, but that implies that SWD could actually be disabled.
