Just because a consumer requests for single open and suspect data, be aware that the application should look at the login response from the provider to confirm what values the provider is actually providing, as some providers may not support one or both options.

Assuming the login response from the provider indicates that single open is enabled, then yes, in theory, the consumer should never receive a closed recover status and the provider will perform recovery. With that said however, there is nothing within UPA which would prevent the provider from sending a closed recover status (other than documentation), so I would recommend to anyone developing a consumer application, to still prepare for the possibility of receiving such a status.

Regarding 'Status' contained within the state filter entry of the source directory, yes, when received, that status must be applied to all open streams within that service. ADS will follow the same rules, meaning with single open enabled, the status will be open / suspect when the service goes down and recovery will be performed in the ADS. With single open disabled, the status will be closed recover when the service goes down and all streams are closed. Same applies for group level statuses. But again, although this is the expected behavior, there is nothing preventing a provider from doing something differently.

Yes, on a closed recover status, the stream (or streams) are closed and it is the responsibility on the consumer to recall.