As you might already have seen, from the linked thread above, this CTD has been happening for quite a while and although i can’t guarantee that it isn’t code within FSLTL that is also causing this issue, I suspect very much that it isn’t.
This CTD appears to be hitting more and more people and can apparently lie dormant for quite a while, before making an unwelcome return. A large number of potential fixes have been claimed, but all these appear to do is to maybe delay its return, so it might just be that a slightly varied memory imprint of MSFS does affect the likelihood of it happening.
Hope springs eternal that MS/Asobo are actually investigating this one and will soon find a permanent fix.