I do not believe there is such a thing on a per-field, per-item level. PIM's ACLs just are't that granular (aside from custom scripting in the SDK).
What you may be interested in is usage of the Catalog system. The top-level view of this is that you create catalogs separate from the Master and direct your imports/enrichment into these "Staging" or "Supplier" or etc. catalogs. When the data has been approved you merge them into Master, not unlike committing to the master branch of a Git repository.
Theoretically; the partitioning of unverified data allows for review of content changes and the ability to reject incorrect data (essentially bad commits). You also may be able to block certain fields.
I am not too much more familiar with catalogs than this as the company I work for does not utilize them. -Just thought it'd help and might be worth looking into.
If you are okie with SDK customization, you can look into "PropertyPreSetter", where you can write your custom logic and reject the change. You can refer "PIM_8.<latest version>_Software_Development_Kit" for more detail on this.
Thanks for your response. Yes, that would be the ideal way to do it, but unfortunately, the way we are set up, having staging catalogs is not an option.