The Wait action just delays the FINISH event on a state so it won't help you in this case.
Ideally you'd use Send Event with a delay of one second and use Set Event Data to store the velocity. Then when the other FSM gets the event it can use Get Event Info to retrieve the velocity.
However there are a couple of problems with this approach:
1) Just found a bug with Set Event Data and delayed events. So that won't work
2) Send Event doesn't have an Every Frame option since this wasn't an anticipated use case. However you can use a Next Frame Event to loop the state...
Anyway, this is an interesting problem! I'll fix 1) above and test your scenario in the current beta. That would make this sort of thing easy to do - which I like
There's probably other ways to do this, maybe storing a buffer of velocities using ArrayMaker...?