Damir if you are using ST3 for lyrics then i would say its a much easier way to program then a keyboard itself.
@davey62 - I agree with Damir's above comment.
If you're thinking of getting to the point of using ST to be the main 'controller' of your band's automation (and backing tracks? Click track? lyrics?) then I'd be going all-in.
If the keyboard player is manually changing presets between (or during) songs, use ST for this.
If you're considering the same to automate your HX Stomp, then go for it. You can start simple and just have it load your patch/preset at the start of a song to get familiar with your gear. Once you are more confident, then you can start having it automate changing of patches/presets/scenes/turning effects blocks on/off during a song.
I've watched as the 2 guitarists in my band have gone through the revelation of how much it 'freed' them from their pedal board during a gig. They're no longer focused on dialing up patches at the start of every song, of hitting that footswitch at the right moment in the middle of the song. Once we had invested some time into (1) understanding the optimal way of 'driving' their respective devices (in my case, it was a Line6 Helix LT and Hoton Ampero II Stage) and getting default patches up for every song, I'd then sit down with the guitarist in my home studio and we'd run through the mid-song changes they wanted to automate, then we'd refine the timing of the changes. That last part was critical as an effect change mid-song is rarely on the beat. I'd always do it a fraction early to allow the few ms for the device to load the new patch and then catch the first note pick/chord strum (which probably is on the beat). Equally, a guitar solo might have a 1-2 bar run into it, or a slide.
Anyway, it depends on your material and what you need to achieve!
BTW, the major thing I learnt in automating guitar effects devices is do no automate a footswitch; automate the actual effects block or whatever the footswitch is controlling.
Footswitch just toggle the state of something. If you can control that 'something' directly (i.e. bypass the footswitch), that is the best option.
Footswitchs are usually a toggle. They change the state of something - if it is currently On, turn it Off. If it is currently Off, turn it On. If you don't know what the starting state is, then you can't be 100% sure when you automate the toggle whether you are turning something on or off. All you are doing is changing the state of it. If a guitarist steps on a foot switch (or a punter too close to stage) and then you toggle it, you might find yourself doing the opposite of what you intended. If you automate the effects block itself, then you are specifically tuning it On/Off. No doubt as to what is going to happen.
The other tip is that depending on the device, effects blocks you turning on/off, that then deviate from the stored preset/patch/scene, if you change to a different preset/patch/scene, and then come back, what state is it in? Are the effects blocks reset to the preset/patc/scene staored setting? or are they the same as what you left them in?
I've found it is better to be safe and revert any automation change made before you change patch/preset/scene. E.g. you turn on a Boost effects block for the outro of a song, then before you change patch for the next song, turn off the Boost. Different devices behave differently, and the behaviour can be different within a device depending on the patch architecture.