~/.config should only be used for configuration data. Run-time data should live in /run (or /var/run on older distros).

Relocating these sockets to /run would also fix the current issue where audio forwarding doesn't work if the user's home directory path is too long. Even something like this is still 26 characters under the length limit:
/var/run/chrome-remote-desktop/pulseaudio#d33e28e995b2030eb8d14f610a02e1e6/native
 

~/.config should only be used for configuration data. Run-time data should live in $XDG_RUNTIME_DIR.

Relocating these sockets to /run would also help alleviate the current issue where audio forwarding doesn't work if the user's home directory path is too long. Even something like this is still 18 characters under the length limit:
/run/user/356925/chrome-remote-desktop/pulseaudio#d33e28e995b2030eb8d14f610a02e1e6/native
 

~/.config should only be used for configuration data. Run-time data should live in $XDG_RUNTIME_DIR.

Relocating these sockets to $XDG_RUNTIME_DIR would also help alleviate the current issue where audio forwarding doesn't work if the user's home directory path is too long. Even something like this is still 18 characters under the length limit:
/run/user/356925/chrome-remote-desktop/pulseaudio#d33e28e995b2030eb8d14f610a02e1e6/native