Answer
Not through permission sets/presentation objects alone — a custom field added to an existing page inherits that page's own security; you can make the whole page (and therefore the custom field with it) read-only for a group, but there's no built-in way to lock down just one custom field on a page while leaving everything else on that same page editable. The two realistic options are: a Custom Event enforcing the restriction programmatically, or restructuring the field onto its own separate custom Logical Unit/page — showing it as a read-only custom field on the original page for everyone, while only users who need to edit it are directed to the separate page (built on that dedicated LU) where the field is actually writable, letting that separate page's own permissions control who can change it.