Limits to Default project

Within our org, we have no way to limit users, some of who are readers, access and spend against the default project. Is there a way to delete the default project or set strict limits?

The only scenario where this system makes sense or improvement is if you create a project and only distribute API keys to non-organization members.

Projects don’t matter to organization reader members, they can bill whatever they create in their account for API keys and their own projects directly to an organization they belong to.