Sorry for the delay, after contacting support in January, here's the answer I got from SmartBear support:
...I got a reply from our R&D team that the Enabled property corresponds to the native hidden method called isEnabled. You can find it and check this. Also, that Return button has the userInteractionEnabled property with the False value. This means that the Touch event will skip this button and will be caught by the parent control.
In order to go further in the investigation, I would have to "share" my mobile app which is problematic due to client/server security certificates and ports.
My final approach with those 2 iOS keys (Return-key and Dismiss-key) was to get the top and left values, add 20 (pixels) to be within the button region and touch it's parent object at those coordinates. This got rid of the warning message generated by TC.
The following code currently ends up in the "else" part.
myTouchParent(Aliases.iOS.myApp.window_X.iOS_WideKbd.KBKeyView('Dismiss-Key'));
function myTouchParent(myObj, StartWithThisObj : variant = nil);
begin
if StartWithThisObj = nil then
myObj.Parent.Touch(myObj.Left + 20, myObj.Top + 20)
else
StartWithThisObj.Touch(myObj.Left + 20, myObj.Top + 20)
end;