General design question to prep for 4.6c -> ECC6

[Sample, Rick]

I have to create a new WF in 4.6c. We will be moving to ECC6 on our 
business side of house next year. Right now, I have the luxury of having

ECC6 in HR sandbox, so I can play around with design in both versions. 

I have a block of logic that can be easily solved in ECC6 but not so 
easy in 4.6c. 

Basic logic: (Keeping details to limit)
In 2 leg fork.

I need to have a background task that will need to wait X time before
executing  
OR 
when 2nd foreground task fork is Approved.
When time = X OR 2nd task in other fork is Approved, 
execute and complete background task and logic block.
The background task can complete, but block must not 
complete until agent has approved foreground task.
i.e. 2 leg fork requiring both forks to complete.

In ECC6, I can easily accomplish this with the new Conditions Tab on
task.
This is the enhanced Deadline Monitoring and works BEAUTIFULLY!
We can now start/complete tasks based on more than just Date/Time and 
if conditions are not met, the deadline monitor re-evaluates every run. 

In 4.6c, this is a tad more complicated. What I have so far is this:

2 leg fork,
1st fork (for background task) is split with another 2 leg fork branch.
sub fork 1 is just a task with a  Request Start time
sub fork 2 is a Wait for Approved Event listener.
Either one will complete fork!

2nd fork (for Foreground Decision task). When Approved, complete task 
and Raise Approved Event for my object. Thus, completing the background 
fork. 

This works fine, but anyone have a more elegant alternate solution for
4.6c? 

I know this is a lot, so if clarification is needed, by all means ask.
This is a design competition. Best solution gets 20 points... ;-]

Rick Sample
SAP Business Workflow Developer
Graybar, Inc.