right. For sessions, you can probably override the session recipe functions like doesSessionExist etc, and cache their values as well on the frontend and in case they fail due to network errors, you could return the cached values.
The only thing to keep in mind here is that you may need to hack around with the value of sFrontToken in the storage to extend its lifetime since a lot of the frontend functions detect that the access token has expired by reading the expiry time of that front token.
The front token is base64 JSON encoded.