Hello @RheaAyase, this issue is already being tracked at #8076. Closing as a duplicate.
You've described Steam doing an expected deferred shader pre-cache update cycle.
Not a duplicate... Come on, read the $subject - different issue :D
OR alternatively change the $subject of the other issue to better reflect the reality :)
Sorry if I didn't communicate as well as I should have. This is the current expected behavior for the Steam client and is when it checks for a shader pre-cache update. The update is deferred until after you start the game so that there's less blocking time while the user is waiting for it.
The general frequency of Steam pre-cache updates is what #8076 is tracking.
This is a common OS-agnostic issue you can easily google for. Happens with many games, but not all - after you close the game, Steam proceeds to forcefully validate files, not letting the user to interrupt this process, also invalidating shader cache, having to either redownload or rebuild it (depending on the game in question).
Possibly related to https://github.com/ValveSoftware/steam-for-linux/issues/10285