Imperative recovery can provide extended information about target NIDs for a client to use, but client has several restrictions preventing it from using that data

1. client uses for mount only config NIDs and fails early if can't initialise initial connection based on NIDs in config file, IR NIDs are not even tried in that case
2. client fails immediately if first NID in IR NID list is not suitable for new connection for some reason, without trying others
3. client fails to mount if IR provides more than 32 NIDs even if they all are good