Yup, absolutely yes.
Wrap a native button with a widget - a user widget that has a simple button inside (or additional elements should you choose to decorate it further, ofc). This way a button can have its own variables / methods / animations and conform to UI styling easier.
Let’s say I need a red X close button in the upper right corner of every window that can be closed / dismissed. I would not use a native button for that. I’ll happily pay the upfront cost of setting it up so I can benefit from easier maintenance further down the line.
Likewise, I’d do the same with an Editable Text. Let’s say I need to emulate an MS-DOS-like terminal interface. Even though Construct Object from Class may seem like a perfect choice here for creating and displaying lines of text, I’d rather have custom functionality built into every line of text the terminal can display - a blinking caret to start with.
Again, it all depends on the scope of what we’re working with. I’d do none of the above in a 24h game jam…
There’s also re-parenting widgets but that has always felt like opening a can of worms 
Some things are inherited, others are not.