The only other option I can think of would be to write a CLI script. Also, please note that there is currently a bug that affects importing of organization vault exports (see work-around here).
Yes.
The better way to do this is to configure the Collections in your Family organization vault so that this additional user does not have any access permissions to view Collections that they should not be privy to (and vice versa, if appropriate, give them access only to Collections for which your other Family plan members have no access).
Organizations are primarily for the purpose of sharing credentials (and other vault items). If you have no need to personally use the passwords created be another organization member (or if the organization members have no plans to share passwords amongst each other), then an organization may not be the optimal approach. Two drawbacks of using a Family plan for the purpose of managing other users’ passwords are first, that by default, all of their accounts will be visible in your vault (and show up as autofill suggestions), and second, that when other users create a new vault item, by default, the item will be stored in their personal vault (where you will not be able to access it via the shared organization vault).
This would be an alternative approach. Technically, it might violate the account Terms, which specify that “a single login may not be shared by multiple people”, but I have never heard of this restriction being policed, and it could possibly be argued that occasionally configuring or maintaining somebody else’s account is outside what they consider to eb a “shared” login.
There was a Reddit discussion recently about a marketing survey in which Premium users were asked the following questions:
Bitwarden Premium User Survey
It is not clear that the price increase is a foregone conclusion, or that it would be in the amount suggested in the survey ($20/Premium; $48/Family). Per the Reddit discussion, some versions of the survey proposed $24/year for Premium.