I only explained the process to highlight the difficulty of making it happen. The OS cannot, on its own, convert a file of any type into a PDF. The program designed to manipulate the file would have to do that.
The OS doesn't necessarily read and write text. It hands that off to a process that can handle it. Whether that is an app or a background process, it still must be rastered into printer commands. It doesn't send a capital "W", then a lowercase "h" followed by a lowercase "y" to the printer. It would have no idea what to do with that.
Office came with Automator Actions that would save an Office document to PDF, so those would be possible.
why would it be so difficult to recognise the command as a command in automator or applescript?
Recognize what command? The command to turn it into a PDF? Well, you would have to tell the default program to turn it into a PDF.
When you Print in the Finder, it calls the default program and tells it to print the document. You cannot intercept that print command to push the save as PDF command on top of it.
Therefore, you would need to create your own commands to tell the specific default program to Print, then use the Save As PDF command. This could be done with UI scripting in AppleScript, or possibly Watch Me Do in Automator, but you would have to parse out which program opens what file type and either tell it to convert to PDF or Print, then click the Save As PDF command.
You can create an Automator Service that gets Files in the Finder, then run your "convert to or print then save as PDF" algorithm. You could give that Service a shortcut. While you may have collected all the underpants, you still need to flesh out Phase 2 in order to Profit.