Funny to read your last post, it's pretty much exactly where I found myself a couple of years back, except we were two electrical guys not one. I did all the micro programming thou, and as such had the deciding vote. I don't think we ever did a micro job that was not PIC based since I had a great deal of experience with them, but I always dreamed of moving away from them over to Cortex-M, for numerous reasons I won't list here. After much too long, after I changed job, I finally made the switch to STM32 and today I only use PICs in special low-power applications or if I want a SOT-23 sized micro like their 10F series.
We were probably 6-7 employees in the entire company at that time, with most of the guys on CNC, and moving away from what worked in the electronics dept. was simply not an option during those years, as you say, everything new becomes a major decision.
Went big; Dumped pic. Got STM32 dev boards, Keil Pro with the middleware, Segger J-Link Ultra, a few third party stacks etc etc. Keil as most people who use it will admit isn't the best IDE out there, but it's far from the worst! It at least consistently works (cough... MPLABX).
So glad I did. I'm just now laying out a small volume product and it's just so much faster to have RTX and middleware up and running day one. I can't believe I wasted so much time on PIC for main micros. I don't care what anyone says, their CAN peripheral is absolute garbage among every software issue they have. Oh well, live and learn.
Still one person team but I can tackle RTOS, USB OTG, File System, etc now with almost no real effort. Everyone talks a big game about this or that, but at the end of the day, you need to get product out the door.
As for the original topic.... OSEK sucks. Unless you need actual OE validation and testing which almost no one does, just use a generic RTOS.
Fwiw.... The PIC 10F series is kinda cool.