In my experience, there haven't been many cases where I can't assign a core or multiple of them to spinlocks, if it's in my hot path.

That said, I probably wouldn't ship spinlocks in consumer libraries or code I expect to be reused across deployments.