AFAICT this only exists because you want to use `LiveScraper` instead of `Scraper` in the cache-miss case?  I think you probably don't ever want to cache liveupdate-specific scrapings so perhaps it'd be better to skip this caching mess altogether in liveupdate? 

If there's a way to make use of the core code when not doing liveupdate-specific embeds then that's fine and good, just don't worry too much if not.

(for clarification, when I asked about the cache params in the r2 patches I wanted to make sure that cache wasn't poisoned because it was in use, but I'm not especially desirous of using the cache here in liveupdate unless it's easy and happens automatically via the scraper system)