A couple of thoughts:
1) Since you are not translating ports, you do not need the "to-port=1194"
2) I'm forwarding to an internal OpenVPN server and it works fine without any other additional forward chain firewall rules. But, if all else fails, give it a shot.
I work with just this (using tcp)
/ip firewall nat
add action=dst-nat chain=dstnat comment=OpenVPN dst-port=1194 in-interface=ether1-gateway log-prefix=openvpn \
protocol=tcp to-addresses=192.168.1.56
3) Need more clarity on exactly at which point it fails ......
a) Does the OpenVPN session never get established? If that is the case, then you should look at both the client and server logs.
b) Or, does it establish and eventually times out because there is no client traffic? If that is the behavior, then I suspect that you have no routes for the OVPN client networks on the MT that point back to the OVPN server. Like this, where .56 is the OVPN server ..
/ip route
add check-gateway=ping distance=1 dst-address=10.0.8.0/24 gateway=192.168.1.56
add check-gateway=ping distance=1 dst-address=10.0.9.0/24 gateway=192.168.1.56