A SOCKS Port Number Doesn't Tell Chrome Which Protocol to Use
Specify the SOCKS protocol explicitly where Chrome supports it. A port such as 1080 or 27977 is just a listening port.
A SOCKS5 service on port 27977 is still SOCKS5. Port 1080 is a convention, not a protocol detector.
When configuring Chrome through a supported explicit proxy interface, the scheme identifies the intended protocol, for example socks5://proxy.example:27977. The SOCKS5 proxy list offers public candidates for that protocol; check the selected endpoint's authentication requirement. A different port does not turn SOCKS5 into SOCKS4, nor does a bare address guarantee that a system setting will be interpreted as the version you intended.
Check Chrome's effective configuration as well as the server's protocol. A managed policy or another running browser process can make a shortcut's edited arguments irrelevant. A separate Chrome test profile makes the intended launch easier to inspect.
Also check authentication before blaming the port. Chromium's SOCKS documentation states that its SOCKS5 support does not include authentication methods. A service requiring a SOCKS username and password therefore has a compatibility issue that a new port number cannot solve.
Choose a compatible client or an approved service arrangement. Repeatedly changing a known SOCKS5 endpoint to unrelated protocol labels only changes the bytes sent to the same listener.