When is eventual consistency acceptable for user-facing features?

We're designing a new feature where users can customize their profiles, including a profile picture and a short bio. The backend is distributed, and we're considering an eventually consistent model for propagating these updates. My main concern is the user experience: seeing an old profile picture right after uploading a new one could be jarring. What are typical scenarios where eventual consistency is acceptable or even preferred for user-facing features, and when should we prioritize strong consistency, even with the performance hit? Are there patterns or techniques you've used to mask eventual consistency from the user in these situations?