Absolutely, yes.

Think about the fact that the primary purpose of a design system is to document the components and interactions that all digital products using the system should apply. For something like interaction states such as hover/on-click/focus/disabled states, you should 100% include those.

Think about it from your developer’s perspective: would you want them to guess what to do when a user hovers over a button or link? Do you have different dev teams? If you do, and they each guess something different, then you have accrued the design debt that design systems are meant to mitigate.

Hope this helps!