It's indeed Stockholm syndrome. It's (Ghidra decompiled) AArch32 firmware, but they define the datatype themselves with that name.

Reading the claroty article mentioning nginx, I think it's more likely that their decompiler is just setup to use windows semantics since that's probably a majority of what they analyze.

Iirc LPCTSTR is just an alias for const char* , lp being an anachromism of "long pointer" held over from the days when needing to do a distinction for "flat" 32bit pointers since there already was "near" and "far" pointers during the x86 16bit era.