Forced Parameterization generating duplicate plans
You will not be able to turn on Trace Flag 4199 in Azure SQL Server. You will get an error message. In fact, you cannot turn on any trace flags (globally or session scope) in the Azure SQL database. At the time of writing this, there were 24 trace flags enabled with Global Scope for Azure SQL database. You can check the list by running DBCC TRACESTATUS.If you want to mimic the same behavior of TF4199 run the below T-SQL statement.
ALTER DATABASE SCOPED CONFIGURATION SET QUERY_OPTIMIZER_HOTFIXES = ON ;
Reference : ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL)
I suggest you read this article:
Understanding Optimizer Timeout and how Complex queries can be Affected in SQL Server by Joseph Pilov
Plus look at the other hints you are getting from running sp_blitzcache and try to resolve those.

Many Rows Table Spool

Table Spool by Hugo Kornelis

Nested Loops Joins and Performance Spools by Paul White



non-SARGables

Non-SARGable Predicates by Brent Ozar

The Two Ways to Fix Non-Sargable Queries by Brent Ozar