Answer
Not directly — permission sets and presentation objects only grant access at the whole page/table level (or to a specific database procedure, if the screen happens to expose one narrowly scoped to just that field, which most don't). The practical workaround: grant the user full write access to the underlying table/screen, then add a Custom Event with a condition scoped to that specific group of users, which raises an Error_SYS error (blocking the save) if they attempt to modify any column other than the one field you actually want them to be able to edit — effectively simulating single-column write access through validation rather than through permissions.