I confirm that such recovery mechanisms are not part of the API, as application code has full control of the case and could perform the recovery in the most convenient way.

A loop of periodic invocations to OpenConnection on a single LSClient object is suitable;
as soon as OpenConnection returns (that is, it does not throw any exception) the connection is established and the loop can terminate.

Note that there is no internal check on the time OpenConnection takes to return.
If adding a custom timeout check should turn out to be useful, however, a new LSClient instance would be needed in order to start a new parallel attempt.

Also note that, unlike the Web Client, upon disconnection the current subscriptions are discarded and will not be automatically reissued after a successful reconnection, despite that the same LSClient object instance is used.