I understand the frustration caused by rat running traffic. The street on which I live was a rat run until a Low Traffic Neighbourhood modal filter, with a signed prohibition of motor vehicles was introduced.

However, we can only record facts in OpenStreetMap. Adding fictitious access restrictions and reclassifying highways in an attempt to break satnav routing is likely to be considered vandalism.

Of particular concern in this changeset, but not an exhaustive list:

w146337398 - this is a highway=unclassified, changing it to service would imply that it is an access road and probably not a public highway. I do not believe this to be the case.

highway=living_street - unless it is explicitly signed as a Home Zone (TSRGD diagram 886) or a Quiet Lane (diagram 884), then it is a highway=residential or highway=unclassified

Private roads should generally be access=private (often gated), or access=destination + ownership=private (not gated, open and routeable for deliveries, taxis, visitors, etc.). Neither should be treated as through routes by routers.

est_width - metres are the default unit, so need not be included. Using a tilde for a range of widths is undocumented and will result in the field being ignored as unparseable. I am not convinced that these roads are at any point as narrow as 1.5 metres.

You added access=destination to a BOAT (Byway Open to All Traffic). It's a public *right* of way, which already had the correct access tags.

Use of discouraged as an access tag - hgv=discouraged is fine if (and only if) it is signed as "unsuitable for HGVs" (TSRGD diagram 820A).

You can find the road signs referred to above in Schedule 11 TSRGD 2016. These signs can also be added to OSM as nodes on the highway at the point closes to the actual sign, e.g. "Unsuitable for HGVs" would be traffic_sign=GB:820A + hgv=discouraged
https://www.legislation.gov.uk/uksi/2016/362/schedule/11/made
https://wiki.openstreetmap.org/wiki/Key:traffic_sign