There is no one here that can answer your question about user statistics, since we don't know they were created in the first place.
But generally, user-created statistics are rarely called for, since SQL Server creates statistics automatically when needed. The cases where user-created statistics makes sense I can think of:
- Multi-column statistics (but you only get density for the second, third and other columns).
- Filtered statistics.
So, yes, if these statistics were created on a whim with a real purpose, you could drop them.
But there are other alternatives. Updating a non-index statistics with FULLSCAN requires a full scan of the clustered index, and it's a table scan for every statistics. Index statistics are cheaper to update FULLSCAN, since in this case the index can be scanned, and the index is smaller.
So you could consider
UPDATE STATISTICS tbl WITH FULLSCAN, INDEX
UPDATE STATISTICS tbl WITH COLUMNS
If you identify that for a specific non-indexed column you need fullscan statistics, you can handle that separately.
I should add that in many places, they update all statistics with the default sample rate and are happy with that. If you can identify which indexes for which you really need fullscan indexes, you can save a lot of computer resources. Then again, determining which indexes you need this for will consume considerable human resources.
By the way, a sample rate of 50 per cent is quite useless. It takes about the same resources as FULLSCAN and sometimes even more.