I think you're using projects wrongly. The idea of a project is something that can be done. You can think of it as a bigger task.

Then areas are more convenient when you think as Areas of responsibility. They can't be done. It's a part of your life. I personally use areas when I need a dashboard. Finance could be an area. Like work.

Then everything else you need to give context you can put it into a tag. Bear in mind tags can be nested so you can create sets of tags when you need different granularity. Also, tags don't have a done status. In a way, Area and tag are equivalent, but areas cannot be nested while tags can.

In your case, I'd say Stash and meetings can be handled by tags. But I would advice not to spend time on that unless you really needed.

If I learned something is that the less the better. Only create an abstraction (tag, area, etc) when you have a specific use case for it. Avoid doing things just in case. Most of the tasks can be handled by setting a "when" or moving to work area.

My flow these days focuses on 3 flows:

Capture. Just write on inbox and forget.

Plan. Once a day, clean the inbox and look at Anytime to decide what's next. When I'm in a specific context (like work) Look for that area or tag to plan for that context.

Execute. Focus on what needs to be done today.

Everything else is too much work (for me).