Versions before v4.2 were all on WordPress, but weren’t made the “official” version until v4.2 – you could opt-in to upgrade to these versions.
We too moved away from Avada. No matter how intense our efforts were to improve performance, Avada’s bloated code just isn’t fit anymore for performance and speed.
It may be one of the most feature-filled builders for WordPress, but its performance is really bad.
You can have a look at their support forum and see that customers are moving away from Avada.
I’m guessing to always get a cache hit (or to get a cache hit majority of the times) you have to enable the Crawler function.
We’ve been looking into it and are upgrading our hosting to a VPS just to be able to run crawler (as shared hosting don’t allow crawlers).
The benefit of crawlers always keeping cache warm and serving cached content to users is insane.