Maybe there's other reasons like Journal3 that may be the issue but either way it's been a headache.
In a certain respect you are certainly right with your accusations, but the problem has to be put into perspective. The cache extension for OC actually works perfectly as long as you don't use Journal 3 and you don't use the crawler, because Journal 3 has a device detection and generates different code depending on the device. In itself, this device detection is not a problem because LScache supports it with the "Cache Varies". However, the crawler is not able to generate the different simulations for each device. It is therefore a waste of time to search for a solution longer so that you can do a cache warmup with the integrated crawler.
If you absolutely don't want to or can't wait until I make my cachecrawler available online, then another crawler could help you, at least temporarily. LiteSpeed has a standalone crawler that, paradoxically, is only offered for Magento. However, this crawler can be used universally and supports at least rudimentary mobile devices. However, it does not differentiate between iPhone and Android devices. The same also applies to webp.
If you have SSH access, you can use this crawler in the console.
Check it out
https://docs.litespeedtech.com/lscache/litemage/crawler/
Btw.: You said that you have problems with insufficient memory. Then you might want to consider using another hosting from A2 Hosting. I use a test server from A2 Hosting for programming. It's also just shared hosting, but I use it to crawl shops with more than 100,000 items and I've never had problems with running out of RAM.