Thanks for the update and I believe I have found an issue in how the commands are manipulated in the new gdb tooling system.

If you change your board.txt, and replace the two debug entries with the below, does this allow the debugging to begin?

# Debugger Patterns
 debug.gdbscript.adapter_khz=2000
 tools.openocd.debug.path={runtime.tools.openocd-esp32-0.10.1-2021.11.11.path}
 tools.openocd.debug.args={params.verbose} -l "{{build.path}/{build.project_name}_DebugOpenOCD.log}" -s "{path}/share/openocd/scripts/" -f "{path}/share/openocd/scripts/interface/{build.openocddebugger}" -c "set ESP32_RTOS none" -f "{path}/share/openocd/scripts/board/{openocdscript}" {initCmd} 

Problem was solved  with help of Simon and the debugger patterns he gave. (Many thanks!)
I attach the boards.txt that finally worked for me in Visual Micro 2022.218.2205 and 2022.429.2200

One contribution to the problem was also, that I didn't had  the option
Visual Micro > Debugger set to Debug: Hardware in all relevant projects.

PS: Also worked with my other batch of TTGOs (DOWDQ5 CPU, the Batch I tried first was DOWDQ6) and leaving D6 in place. 
(Simplified Cabeling mentioned by kiromaisus: https://github.com/Xinyuan-LilyGO/TTGO-T-Display/issues/6#issuecomment-899104385)

See also attached photo. (If you do the same, don't forget to insulate the header pin used for GPIO 14 against the ground conector on that place on the board e.g. with a piece of shrink tube.)