Would forced parametarization help?
This can be easily checked. Here's code which should imitate your scenario:

ALTER DATABASE [playground] SET PARAMETERIZATION FORCED WITH NO_WAIT
GO
CREATE SEQUENCE dbo.Seq1  
    START WITH 5  
    INCREMENT BY 5 ;  
GO  

CREATE SEQUENCE dbo.Seq2
    START WITH 5  
    INCREMENT BY 5 ;  
GO  

DBCC FREEPROCCACHE()
GO

SELECT NEXT VALUE FOR dbo.Seq1;  
GO
SELECT NEXT VALUE FOR dbo.Seq2;  
GO


Now if you check plan cache:

SELECT text, plan_handle, qs.execution_count FROM sys.dm_exec_query_stats  qs
CROSS APPLY sys.dm_exec_sql_text(qs.plan_handle) as qt


You can clearly see there are two distinct plans for two sequences:


This is what I expected. It works only for parameters and not for object names.