Lock / Hide Tags Field in Core Workflows

Do you have a use case for that idea? Sounds interesting, but I never was in need for it. Because in the end, I rarely use tags and usually suggest using custom ticket attributes for most scenarios.