Trident 250 Becomes Unresponsive During *some* long-ish prints - and 1 more issue

[hot folio]

Sorry for the weird title - there's a character limit that I couldn't figure out how to get around.
Basically, I built a Trident 250 around two years ago from an LDO kit, and for the first year and a half or so, it worked very well for me as a printer. However, lately I have been having two issues whose root cause I have not been able to find.

Issue #1
The first issue is that during some prints, the printer will completely stop printing and become entirely unresponsive. I can't push any buttons on my KlipperScreen, and I can't access the printer on a browser. I have to power cycle the printer entirely in order to get it to respond at all once this happens. It doesn't seem to happen at a consistent time or consistent layer height. It just stops working for some reason that I can't pin down. I do seem to have better luck with prints if I power cycle the printer before starting a print, but that doesn't always help me - and I just had a print fail after ~3 hours, at 83% completion even though I did power cycle the printer before starting.

Issue #2
The second issue is that when I have the printer start a new print, it will just fail to actually start the print for no apparent reason. Specifically what I mean by this is, the printer will go through the homing process, z tilt, and adaptive mesh probing sequence - all at the correct temperatures, but when it is finally waiting for the nozzle to go from 150C (my bed probing temp) to the print temperature, it just won't ever start the print/do the nozzle purge. I have waited 30+ minutes after the nozzle gets to temperature to see if the print will start and it just doesn't. The printer remains responsive during this time, unlike with issue 1, so I believe they are not directly related. Typically, I will just use the 'emergency stop' button and rerun the print (I can rerun the original file and it will work).

I am running out of characters for this post, so I will add additional info in the comments.

I have included the klippy.log and moonraker.log files if that's helpful. Additionally, since I have reinstalled the whole OS and redone the klipper install, I am currently on a much more recent version of everything than I was when these issues first started showing up. However, when these issues did start popping up, they both showed up around the same time, and they both started happening when nothing about the printer had changed.

Printer Hardware
LDO Voron Trident 250 kit (Rev. A)
Bed Probe: ChaoticLab CNC Voron TAP
Hotend: Phaetus Rapido 2 HF
Klipper Host: Raspberry Pi 3B (the Pi doesn't recognize that it has a wifi controller onboard, so I can't hook it up to wifi - maybe that points to the issue?)
Printer Control Board: BTT Octopus Pro V1.1

Printer Software
Klipper Version: v0.12.0-396
Klipper-Adaptive-Meshing-Purging Version: v1.1.2-13-gb0dad8ec
Mainsail Version: v2.13.1
Mobileraker Version: v0.4.0-91-g1d1e2ebe
Moonraker Version: v0.9.3-3

Printer Connections/workflow
The printer is connected to my local network via a 1Gbps ethernet connection (refer to above statement about wifi not working) to my router, and the Raspberry Pi has TailScale (this was recent, and installed long after these issues presented themselves) so I can connect to it with my phone from anywhere.

Before the recent reinstall of all of the software, I typically would slice all of my files with either PrusaSlicer or SuperSlicer. Since reinstalling everything, I have switched to OrcaSlicer. For all slicers, I slice the file on my PC and send it over the network directly to the printer.

Troubleshooting steps I have already taken
As far as troubleshooting goes I have done a couple of things already. I have previously looked through the klippy.log file, but didn't see anything that was obviously wrong, though I am certainly no expert (the attached file is a new one I haven't looked at yet).

I have not seen any errors in the console on the printer's URL either so it seems to me like the printer doesn't even notice the issue is happening.

I also thought that issue 1 may have been happening due to some updates going wrong or something, so I completely reinstalled piOS lite and reinstalled klipper on the original microSD card. I copied my configuration files over, but it was a fresh OS install, and I used KIAUH to install pretty much everything else. This didn't seem to help at all.

I thought that issue 1 might be caused by the microSD card going bad, so I bought a high endurance card (though I cloned the old card to the new one instead of a fresh install) and that hasn't helped either.