In theory, you could build an infinite loop in Flows (although not the way you've built yours). The idea is that at the "end" of the Flow, you add a pause/wait, and then on resume, continue back at the beginning of the flow.
I do NOT recommend this.
In practice, you will eventually (and rather quickly in some cases) run into a limit. Every time a Flow pauses, it deserializes the state of the Flow and saves it to the database, so that upon resume, it can serialize that state and resume execution. The size of this deserialized state will grow and grow upon each pause, and there is a limit to the size of the deserialized state that can be saved to the database upon Pause. Eventually, the Flow will fail because of this limit.
Why can't you schedule this Flow to occur at intervals? This has the effect of infinite loops, but occurs at a predefined time.
If your needs are to be more granular than the Once-a-day scheduling capability of Scheduled Flows, then you'll need to move to Scheduled Apex, where you'll have more granular scheduling options.