I think you already know the answer to your question, which is: no, there’s no magic to rebooting weekly for efficiency. If it were really necessary, the OS vendor themselves (I guess Apple in this case) would be recommending it.
Obviously I don’t know much about your company, so I don’t know if this will work for you. But my suggestion would be to quantify your lost productivity and raise that issue through your management structure. For example, if it takes you an hour after each forced reboot to get your environment set back up the way you like it, then you can ask your manager whether they’re willing to sacrifice that hour of your time on a weekly basis, or whether they’d instead like to take up that issue with the IT department.
This really shouldn’t be your battle; this should be a business decision.
Just don’t be shocked if the answer comes back that, yes, the company would prefer you to spend that hour reëstablishing your sessions, etc, rather than to have the IT department change their policy or make an exception for you.
As others have (very validly) pointed out in their answer, not rebooting for months isn’t really an option, so perhaps you can come to an agreement that you’ll reboot every other week, but at a time of your choosing, and if the uptime exceeds a certain amount (perhaps three weeks), then the automated system can reboot.
I’ll add that I have an intense dislike for “IT Voodoo”, aka operating a computer based on superstition or belief without testing. If you feel it appropriate in your company’s culture/environment, you could challenge your IT department to quantify their belief that rebooting on a set interval is necessary. But I expect this will go nowhere.
