Unfortunately I do believe there is any way to do something like this directly.

But here’s an idea…  I have a process that needs to wait for a database change that could be anywhere from a few hours to several weeks after the user task starts.  I have it running a non-interrupting timer every 24 hours that calls a Workflow (so it’s limited to one extra path in the Form monitor per day).  The workflow runs a loop and checks for the database change every fifteen minutes (so the extra logging is in workflow not the Form) - no changes means keep looping (maxing out just under 24 hours) - if it is changed, end the loop and push a value back into a Form field - if it never changed, the loop ending just under 24 hours ends the workflow without pushing the value back to Forms.  So the workflow either ends with a field value being populated when the database changed or just before 24 hours with no field value.  After the workflow, a gateway checks for the field value, if it is not there, that path just ends (to be started again with the next timer event).  But if the value is there, it throws a signal, which in turn is set to interrupt the user task.  It’s a little complicated, and kind of annoying to have these workflows just in an ongoing waiting status - but it met the need and I only ever have about a dozen of these running each month.