

-
Not a node, but a proxy. Entry node’s IPs in Tor are publicly known, so they are easy to censor. With Snowflake you create a proxy (bridge) between a censored user and an entry node, and since your IP is not listed as a node, you help the user bypass the censorship.
-
In theory, nope. But if the user is doing something bad, a prosecutor could argue you helped them to do so. I don’t know about any case like this involving Snowflake, and I am not a lawyer. You could be a target if you were to host material, which is not the case with Snowflake.
In case it helps, I’ve been running the extension with no trouble that I’m aware of for a few years.
I don’t see why there should be any problem, as they use different ports. Plus I’ve had no troubles running a Jellyfin and Navidrome instances, plus some other self-hosted services alongisde Snowflake.
I’m really glad to have helped you :). Tor is very mystified, but an awesome tool, and very neat from a technical point of view. In case you haven’t seen them, I recommend these 2 amazing videos from Computerphile: How TOR works and TOR Hidden Services