Guidance on isolating a crate from its optional dependencies (alternative: a crate family)

During the development of a library, I found the question asking for Guidance on optional functionality: crates vs features here in the forum. The answers given there focused on two topics: "Features need to be additive"; and "The discoverability and self-documenting abilities of features are really really poor". Both are not a problem for me, so I used features, and ignored the answer saying "Where I work, we've stopped using features with our code. It's not something being dictated. It's jus...