I doubt you'll find any solution without a third party job scheduler. Even with a "wrapper" report this would be quite challenging (how would you schedule the wrapper itself?) and might even defeat the purpose. Why exactly is this a requirement anyway?
The "No Start After" is very frequently misunderstood, make sure to hit F1 and read the documentation. It does not prevent the next job instance from starting after certain time, it only applies to the current job instance. You can do a simple test for this and will see easily that when you schedule a job to run at time X with "no start after" = X + 5 minutes and run periodically every minute, then as soon as the job starts, the next job instance will get scheduled with the release status. And if you check that job you'll see that "no start after" is not the same (X+5) but [the new job start] + 5.
I'm not sure actually what this option is for exactly, it seems completely useless and also confusing (you're not the first person to think it prevents the periodic job execution at certain time of day).
"No activity on the weekends" can be easily achieved with the calendar though.