Eager loading with one-to-one associations does not always set EntityHolder.IsLazy to false

Eager loading with one-to-one associations does not always set EntityHolder.IsLazy to false. As a result, Lightspeed attemps to load an associated entity again. It only happens when the associated entity does not exist in the database.

I created a Sample Project. It has two entities Fruit and FruitMeta with one-to-one association. When I create a Fruit without FruitMeta and try to load it with eager-loaded FruitMeta, it make an addition query in order to get FruitMeta. No other call should be made because the FruitMeta is loaded eagerly. IsLazy is set to true on the EntityHolder (supposed to be false).

This is what I found debugging the source code:

EntityLoader successfully sets IsLazy to false in the MarkEagerLoadsAsNonLazy method. However, IsLazy property still returns true because IsCollectionProxy is true and ProxiedCollection.IsLazy is false:

public bool IsLazy
{
    get
    {
        if (IsCollectionProxy)
        {
            return ProxiedCollection.IsLazy;
        }
        return _isLazy;
    }
    set
    {
        if ((_value != null) && _value.InTransaction && !value && _isLazy)
        {
            _value.BeginEditInternal();
        }

        _isLazy = value;
    }
}

Expected result: There should be no attempt to get FruitMeta if it's already loaded eagerly.
Replicated Lightspeed 5 and 5.5.3381.0