About shouldnt fail if tap isnt configured

This might be an implementation problem but I saw it twice today that running --about without a configured tap causes it to fail. I wonder if theres a way for the SDK to print without actually executing the taps discovery. Or try to execute the tap discovery catch it and return nothing not streams if its not configured.

My use case is to check the taps capabilities and settings without actually configuring it.