I think part of the problem is that many IT departments have a culture which focuses on the needs of less-technical users. They often don't have a good appreciation of the more demanding needs of technical teams. Non-technical users need a lot of handholding – an approach which can be irritating to the technically advanced. A locked-down UI which doesn't let you change any settings may be the right approach for non-technical users, developers can find it infuriating that you won't let them try to solve their problem themselves, and instead force them to talk to a helpdesk who don't understand it either and want to follow some script ("Have you tried rebooting?"), before they let you talk to someone who actually understands what is going on
Maybe software like Jamf isn't inherently a problem, but it can encourage IT departments with that kind of culture to do more things to irritate developers (like automatically run buggy scripts on developer laptops without any notice or easy visibility into what those scripts are and what they do), which without that kind of management software available to them, they would have been less likely to try to do. Developers are more likely to have configured their environment in custom ways which will cause IT's buggy script to play up and cause problems
I used to work for Oracle, and while I was there Oracle had a whole separate IT department just for the engineering/R&D org, while the main IT department serviced the rest of the business (sales/support/finance/legal/HR/etc). I don't know whether Oracle still uses that setup, but (if the company is large enough to sustain it) that could be an approach to avoid some of this