I think it works the same in blixt. It's slower there, but my channels are more functional (which may be because I currently only have a private channel with SN on Zeus, not sure) and it does a better job at keeping the background service properly working on graphene.

Fun fact: many users think that this EGS thing is a weakness for Zeus and they always compare it with Phoenix that is always ready when you open it.

But they do not think what actually does that graph sync at startup or they do not care too much. The graph sync locally on user device is a big difference than Phoenix model where the graph sync is on the Acinq server side. That's why Phoenix knows all the txs where/from are going.

Is well explained here:
https://docs.zeusln.app/for-users/embedded-node/privacy#client-side-path-finding