Yes it’s safe to kill the process; however that doesn’t mean it doesn’t have consequences.
If you lock your system (with it killed), you’ll get an error message instead of the intended lock procedure… ie.
An error occurred starting screensaver. Action ‘activate’ failed.
Ensure you have xscreensaver installed and running.
as xscreensaver performs the LOCK function. The initial login/greeter is performed by the DM (display manager) but it doesn’t handle the locked session.
This is something didn´t know I have to admit.
Thanks for the clarification.
Considering all the facts I think it might be best to leave things as they are right now.
I was just wondering why a process referring to xscreensaver was running but that´s clear now.