Oops I forgot that Sovol has hamstrung their version of klipper by preventing some normal functions. The runtime configuration does not appear in klippy.log on your SV08.
To understand why your machine acts weird you need to check many files.
[include macros.cfg]
[include mainsail.cfg]
[include timelapse.cfg]
[include get_ip.cfg]
[include plr.cfg]
[include moonraker_obico_macros.cfg]
It is possible that additional files are [included] from those files. Makes it so the log is no longer a stand alone diagnostic record.
In the event of an error there automated tools to extract “shutdown logs” from the routine data in Klippy.log
There is also a graphing tool that can be useful when debugging setups.
As for reverting to stock… I’m a strong proponent of “if it ain’t broke don’t fix it” but as you don’t have a handle in what is changed and the need for custom start g-code in your slicer you may be happier with the “known” setup.