Can't use sidekiq-cron directly with superworker because it requires a job id and process

[FeminismIsAwesome]

Right now, a superworker can only be triggered via perform_async class method call. I'd like to add my jobs via sidekiq-cron (https://github.com/ondrejbartas/sidekiq-cron) but sidekiq-cron uses the instance method perform entryway in order to kick off a job by putting it on the queue. This means that currently, i have to create a proxy job that kicks off the static superworker in order to get it enqueued correctly by sidekiq-cron. I'd love for the ability to just kick it off from sidekiq-cron directly. What work would be required for that? I'd be willing to make the pull request if you had a way to point me where to start. Seems like WorkerClass would be the entry point?

Cheers,
Ian