Limitations of database context pooling in .NET

I have a base class called BaseDbContext. I derived two classes from this: WriteDbContext and ReadDbContext. Both contexts have compiled queries as private members in WriteDbContext and ReadDbContext:

public class ReadDbContext(DbContextOptions<ReadDbContext> options) : BaseDbContext(options) 
{
    private static readonly Func<BaseDbContext, string, string, Task<SampleDto>> SampleQuery =
        EF.CompileAsyncQuery((BaseDbContext baseDbContext, string id, string name) =>
            baseDbContext.Samples
                .Where(c => c.Id == id && c.name == name)
                .Select(c => new Sample
                {
                    SystemId = c.SystemId,
                })
                .FirstOrDefault()
        );
    
    public async Task<SampleDto> GetSampleAsync(string id, string name)
    {
        return await SampleQuery(this, id, name);
    }
}

WriteDbContext also contains the same exact code.

Can I do the following things when I want to use DbContext pooling:

1. Use private fields like compiled queries in context classes
2. Make use of HttpContext.Items to store some information to log

What are all the limitations of DbContext pooling?

edit:

I build APIs. The application serves a lot of traffic and I want to achieve more performance so that is why I want to look into database context pooling.

I read this article https://dev.to/mohammadkarimi/how-dbcontext-pooling-works-4goc and similar other articles which talked about the limitations I mentioned. So, I wanted to know more information about how storing something HttpContext.Items and private members affect database context pooiling

There are two different connection string of reader instance and writer instance. So, I think I have to have two contexts.