Well after reading your latest post, I went back to the original, and there's no way I could've possible read the 1st post to be close to what you're wanting in the 2nd one.

I didn't run this script or change my clock to test it, but it should work.

What this alias does is check the current time that it's running, then sets %day to the 3-letter code for the day of the week, Sun thru Sat, and sets %now to be the current HourMinutes. It then creates %next as whichever is the next closest future time of the day between these 2 times, so obviously the variable contains a time between 950 and 1149 then the next nearest time will be 11:50, but otherwise it would be 09:50.

If the alias runs at 9:50am on Sun or Fri, the echo is where you can put your 'do stuff'.
And likewise, if it runs at 11:50am on Mon or Thu, there's another echo for that stuff.

But regardless of whether it matches any of those day/time combos, it then launches the timer again trying to execute at the next time window.

The syntax for timer lets you either set it to run at a specific hours:minutes within the next 24 hours, or to run at a specific number of seconds in the future. It's a lot simpler here to let it execute on each day of the week, but only do things on the correct days.

I have no idea what you mean by putting the script on the name, or doing a checkup. So that's probably in the place for the 'do stuff'. Depending on what you want to do those 4 days, it might be needed to split the Sun Fri trigger into 2 sections.

Code
alias DJtime {
  var %now $asctime($ctime,HHnn) , %day $asctime($ctime,ddd)
  var %next 09:50
  if (%now isnum 0950-1149) var %next 11:50

  if ( (%now == 0950) && ( $istok(Sun Fri,%day,32) )) {
    echo -s do stuff at 950am on Sun or Fri

    goto next
  }

  if ( (%now == 1150) && ( $istok(Mon Thu,%day,32) )) {
    echo -s do stuff at 1150am on Mon Thu

    goto next
  }

  :next
  .timerDJtime -o %next 1 0 DJtime
}