Now I'm just guessing here, but it seems likely that every time you force an update by using the above link you're leaving the update ring to which you belong. Hence when your Teams app is idle and the client does it's own background checking for ring/available version you end up with another version/back to your ring. Is that something you could verify when being "kicked out"? You would have to look in the Teams log (right-click on Teams icon in taskbar).
As a general approach you shouldn't tamper with the version as the Teams app will take care of that itself. Teams is simply not as other software where new features are controlled by latest release, but rather decided backend OR by using the Public Preview/Dev Preview. The former is controlled by a the Teams update policy and the latter by the Teams setup policy. They are pretty much the same thing.
On very few occasions this hard force is done to make a new feature appear more promptly, the more official way to "force" though is from within your client by checking for updates.
Hope that makes the whole thing a bit more clear.
Adding this for reference
https://techcommunity.microsoft.com/t5/microsoft-teams-blog/microsoft-teams-release-processes-why-do...
