If you want to start over create a new airframe. Every airframe will restore its last state by default, it’s persistent. If you want it to be in a different state you have to put the plane in that state and save it for later use.
The key is to get at least the Max variant, with the most GPU cores available, and 24 GB of unified memory if possible. Anything less will likely struggle to get good X-Plane performance.
Network sync of aircraft state will never work properly for addon aircraft. I don’t know about your specific setup/issue, but TBM most likely needs to only be run once on the main computer with the controls and avionics displays.
Last backtrace isn’t similar, points more at the sim itself, which would require reporting to LR. However as you have many plugins you’ll need to remove all third party plugins except Gizmo64 in order to test on a “clean” system.
The SAM plugin is highly likely to crash X-Plane. This will need to be removed before we can troubleshoot reliably. There is an alternative available as SAM is no longer supported by its developer. https://forums.x-plane.org/index.php?/files/file/90865-opensam-an-open-source-replacement-for-sam/
Ah ok. If using Xsaitekpanels, or similar interface, plugin I suggest removing all the default functions, if they’re still in place.
Can be in basic function, there’s commands for all the FCP functions.
The configurator is the only way the autopilot controls on the Bravo can be used as intended, which my profile does. The course selector moves the course knob, which isn’t always what one needs/wants.
When one uses "toggle reverse" one must move the throttle levers forward to add thrust above idle. The thrust reverser levers on the Bravo are simple switches, as it sounds like you've discovered. (Which is why I'm not sure what "no 8 and 9 levers (T. Reverse)" means.) Otherwise it does sound rather broken. I suggest stripping the sim back to defaults; remove the bridge plugin and any other Lua scripts, unbind everything in X-Plane, and start over.