Noooooooo!
Not only should you not want 2 Ticks, you should never want ANY Ticks.
Check out Timelines. These are what you use when you need a perpetual process. Why? They can be started and stopped at any time, meaning you can save processing when their corresponding functions aren’t needed.
Also, they’re AWESOME! You can set the length of the Timeline you create to anything, or you can set it to loop so it goes until it’s stopped. You can even create graphs and set specific times for new events to fire off within the Timeline editor and output those values from it! If that’s not enough, you can stop and start again where it left, start from the beginning, reverse it from the point it stopped, or do a pure reverse from the beginning. They’re incredibly useful.
Save your Tick for printing string values of input and stuff like that. Even when you’re testing new mechanics, though, use Timelines instead of Tick. It’ll be more frustrating to go back later and change your systems when you’re optimizing for performance. Do it now, learn it now, and build everything with solid foundations.
Trust me on this. We gained huge performance boosts by eliminating literally all instances of Tick and replacing them with event-triggered Timelines.
Here’s a link to the Timeline documentation: