Answer
Not reliably — if a user has access to the column chooser (or Aurena's equivalent), anything you hide for them at the view/list level can simply be reopened by that user, since it's stored as a per-user preference rather than a real permission. The only way to genuinely restrict visibility for a subset of users is a client-level customization that filters the retrieved elements based on your own logic (e.g. permission set or profile), and even then you should weigh whether removing the field could break some other action that depends on that data being present.