As a customer, the resource-based pricing model for the Pulumi service doesn't make sense. I think long-term it's doing more to hurt Pulumi's adoption.
As an organization, the more we use deploy infrastructure with Pulumi, the more it will cost us.
This encourages us to 1) Be more selective about when to use Pulumi. 2) Not invest in the Pulumi service or any features offered by it.
This effectively limits our use of the Pulumi Service to a state-hosting service, further devaluing it and encouraging migration out of the service. The recent changes to the S3 state backend is a nice investment in treating migrating projects in and out of the service as a first-class use case (which will likely be a necessary step for customers looking to reduce their Pulumi costs).
Against our existing projects, the orphaned resource tool sounds like finding change in the couch.