Not that I know of. This feature was requested by other clients earlier, we have repeatedly brought it to the Product Management / R&D attention (and there may have been other clients and partners who have requested the same), but it never came to fruition to be actually implemented in the product (at least yet).
However, if your implementation already requires the usage of a post-process node after the communication node (for whatever reasons), you can make that post-process node double-check that recording to the Contact History happened (or did not happen) like you needed it to be for this type of communication, and raise an error if it isn't. Basically, this post-process node becomes the 2nd line of self-check / control, which makes accidental user errors less likely.
For example, one of our clients is using "Email" communication definitions and "Digital" communication definitions that export data to be used in various digital channels. Email always requires recording to the contact history, however, only some "digital" campaigns require recording to the contact history - others don't.
In this implementation, we require users to use a certain Post-Process node after every communication node (for unrelated reasons). Without a post-process node, nothing is actually sent the channel - so users never forget to add a post-process node (it's a non-issue).
So instead of just one post-process node, have defined two slightly different processes, both available as custom nodes (added to the palette):
"Post-Process (with contact history)"
"Post-Process (no contact history)".
The users are encouraged to manage the "update contact history" checkbox according to the channel and campaign needs, and also use the appropriate Post-Process. If they use the first post-process ("with contact history"), but the out-of-the-box checkbox on the communication node was accidentally disabled, the execution will fail. If they use the "no contact history" post-process, but the checkbox is still set - the execution will also fail. Also, if they attempt to use the "no contact history" process with the Email channel, it will also fail (but for the Digital channel it is OK).
This way we minimize a chance of a user error by making it the selection very explicit in two places and also making sure that the status is clearly visible on the diagram itself - without going into the details of how a communication node is set up internally.
Hope this helps.
-------
Dmitriy Alergant, Tier One Analytics