Perhaps added in 3.5 to accommodate and prepare for a future move… Adding it early makes sense if you want plugins to start using it.
If I search for actionscheduler in the CC files there are a few mentioning it
But I can’t find any reference to the database tables, hence my confusion.
If at all possible CC may as well not use it and remove it’s code, from a technical point it adds nothing extra or special that wp-cron can’t handle. And even if wp-cron is not 100% accurate, just schedule a cron job to trigger wp-cron every N minutes to fix that. Any serious website admin should do that anyway… Which makes actionscheduler even more ‘useless’. IMHO.
Then, if it should be required to use WC plugins in the future, add a translation/conversion layer in the fake WooCommerce that catches actionscheduler things and puts it into cron or something.
I’m not at all familiar with actionscheduler, but I can’t imagine that being very hard.