I do get your point, it's better to think of modularization from the perspective of modularization and boundaries, where EACH module standalone represents a domain concept in isolation. While it can make sense to isolate either "networking" or "database" into their own modules, 'domain' typically isn't and shouldn't be a singular monolith.

As for feature-based reusability, re-use is only a value if the code is actually being reused, otherwise it's design overhead. Sometimes, writing the same code twice is still cheaper than creating some elaborate configurable mechanism that will never be reused.