Sorry, s/session/request/g; corrected above.
One example is a multistep transaction processing request. The feature flag could gate several branch points.
A memory-mapped SQLite file is great too, but the strategy I describe above is less code, quicker to implement, and should get you a very similar performance improvement.
I can see why you need to check multiple different flags in a session and I understand the parent point about looking in SQLite for them (effectively a function call into a library in process address space rather than a call over the network for each flag).