Seeing as at least one root cause is Third Party content, this is getting moved to Tech Talk where all troubleshooting should start.
i fixed my issue after changing my yoke bindings profile back to default
Just an update on my current status for everyone, that some may find beneficial:
I’ve been basically stable and working normally for the last several months.
I resolved the original issue (unable to launch from anywhere in NE US) by completely wiping out my nVidia drivers, including the DX Cache, and performing a full fresh install of the Studio Ready drivers (as opposed to the Game Ready). It’s been my general experience with MSFS that the studio variants tend to be more stable. After performing this action the original issue resolved. Once I did this I was immediately able to launch from the previously discussed areas that would cause a CTD and can launch from anywhere without issue ever since.
However some stability issues still persisted (unrelated to my original post), with random CTD’s (typically when performing a GPU/CPU intensive activity). I WAS able to essentially halt these issues by downclocking my GPU (The above stated RTX 3080 ti) to the ACTUAL factory base rate (1650Mhz). Although unrelated to the original issue, It seems nonetheless my previous GPU downclocking efforts where not QUITE all the way back to the actual factory clock, and as soon as I downclocked back to the actual factory clock rate of 1650Mhz I stopped seeing any in-flight CTD’s. In fact I was able to push it to 1680Mhz and have had no issues at that rate either, but any higher is almost like an absolute dead threshold and the stability issues come right back. After some research it appears that a core kernel windows update sometime in 2022 introduced a stability issue with several game/sim platforms with factory set overclocked GPU’s. To downclock I use Afterburner, which applies the downclock at launch of the windows UI. Another way to do it is to use “Debug Mode” from within the nVidia control panel (Help–>>Debug Mode), this will downclock any factory GPU OC’s back to the base rate. Once you are in “Debug” mode you can open Afterburner and see what you’re actual factory base rate is, and then just use afterburner to apply the downclock at windows startup.
Since the above I have seen no more CTD’s during the last 30-40 flights, most averaging 7-8hr and some as long as 16-18hr NAT track flights. I’m able to fly on Vatsim without fear of dropping off the map 
I still do have one CTD issue that persists, but since I know exactly what triggers it, it hasn’t really been a factor. It’s one which I see many have and seems to be related to a bug that still hasn’t been resolved. This being whenever using the satellite overlay in the world view, when zooming in I will occasionally have a CTD. I’ve just made it a habit to always switch off the satellite overlay as soon as I enter the sim/world view. It w/b nice if this was fixed once and for all though.
So, in a short summary:
Original issue of CTD at specific locations:
Solved by a complete wipe and fresh re-install of nVidia Studio Ready Drivers
Stability issues / intermittent CTD during flight, when high GPU/CPU demand:
Solved by downclocking to the actual factory base rate of the GPU
Hope there is some info there that may help some, if anything further develops I will make a new update.
-C