Hmm, I also have Tasker installed, but had never enabled it in Accessibility Services...
Now when I tried to enable it (and only it) - it did have the same effect, i.e. breaking keyboard in the same way. So it is not Automate specific and most likely linked to Samsung keyboard itself, since another keyboard I have does not have any problems when either Automate or Tasker are enabled in accessibility.
Sorry for false alarm...