GameObjects are not always culled when outside the Camera's frustum

Reproduction steps:
1. Open the attached “IN-48510 Frustum Culling.zip” project
2. Open the “IN-48510_FrustumCull_Bug” scene
3. Enable the Statistics overlay by pressing the “Stats” button on the Game view Control Bar

Expected result: The “Cube” is frustum culled and the Statistics in the Game view display “Tris: 2”, “Verts: 4” and “SetPass calls: 1”
Actual result: The “Cube” is not frustum culled and the Statistics in the Game display “Tris: 14”, “Verts: 28” and “SetPass calls: 2”

Reproducible with: 2021.3.29f1, 2022.3.8f1, 2023.1.10f1, 2023.2.0b6, 2023.3.0a2

Reproduced on: Windows 11 Pro (22H2)
Not reproduced on: No other environment tested

Notes:

• Different Rendering Paths used by the “Main Camera” produce different triangles' and vertices' amounts but the issue still reproduces the same way
• Field of View and Near Clipping Plane settings of the “Main Camera” change the Position and/or Rotation the Camera needs to be at to reproduce the issue
• Could not test in Player due to the “Cube” GameObject not being visible on the screen whenever the issue reproduces or not