It it needed in the case when route is something like /users/profile
When it is /profile, it is unnecessary.
We should choose which route should be used. Let's consider pros and cons, you are welcome.
/profile pros
1. It is plain. We have a requirement that only subject can have profile, /users/profile can mean that every user can have profile.
2. /profile means "my profile". I can send this url to person and say - hey, dude, that what you need to fill in. Don't need to find his id to compose correct url.
3. We can divide logic for admins /users/{id}/profile urls (which are needed to see information about victims) and subjects (which are allowed to edit only their own profiles) /profile url by natural way, without dancing inside controller to check if we modify this and not modify that. But, of course, this pros is arguable,  I dunno opportunities of IR to protect resources.