>After having done more research on this, I found that even with using a "exec sp_executesql" approach for all data accesses at the framework level, it was not changing anything in regards to that specific situation. So, I put back OPTION (RECOMPILE) and it resolved the issue. So, either with native a SQL command or from a stored procedure approach, both had the same problem and both were ok with the OPTION (RECOMPILE).

The sp_executesql helps SQL Server to reuse cached execution plans because it clearly separates a query and its parameters.