I’m sure others will have better ideas, but I would start by creating a “Recurrence” number field in my tasks, as well as a “Recurrence Period” field, and a “Re-Open Date” field.
So your task could optionally have as an example, a:
Recurrence Period: Month
Recurrence: 3
For a task that is meant to recur every 3 months. The period could be “year”, “day”, “week”, etc.
Then, and this is where AI might help, but I would create a formula that runs every day – It would scan for Tasks with Recurrence Fields filled, and would see if the proper amount of time had passed for the recurrence.
If so, you could either Re-Open the task, create a clone of the task, or some other such thing.
This could get quite complex depending on the logic you want to support. I could also see it being as simple as a single field that represents the number of days between reoccurences, which would cover simple scenarios pretty easily.
To @Chr1sG 's point, depending on how you want the logic to support (allow for “Recur the first of every X months”, every “X years”, clone the existing task vs re-opening the old one, etc) the setup would probably change quite a bit. There’s probably not a consensus on what anyone “would expect [recurring tasks] to behave in normal project management tools”