Setting Content/Read with Limitations for User Group affects the list of available siteaccesses to choose from when clicking on "Page" tab, but accessing Page Builder by clicking Edit on Landing Page content results in Landing Page being displayed in the first available siteaccess (not necessarily available on the list) that may lead to unexpected results.

Steps to reproduce
1. Clean 2.4 installation.

2. In Content Root create two Folders, one named Site Root, other Editor Root.

3. In ezplatform.yml set:

ezpublish:
    #...
    siteaccess:
        list: [site, editor, admin]
        groups:
            site_group: [site, editor]
            admin_group: [admin]
        default_siteaccess: site
        match:
            URIElement: 1
    #...
    system:
        site:
            content:
                tree_root:
                    location_id: 57
        editor:
            content:
                tree_root:
                    location_id: 56
       #...
       admin_group:
            #...
            page_builder:
                siteaccess_list: [site, editor] 

Please note, that location_id for tree_root may has to be changed corresponding for your Editor Root and Site Root folders location id.

4. Go to Admin / Roles. Set Editor Permission to:

5. Create user Editor in Editors User Group.

6. Create Test Landing Page in Editor Root Folder.

7. Log in as Editor user.

8. Go to Home/Editor Root/Test. Click on Edit.

Result
Even when clicking on Page tab shows only editor siteaccess clicking on Edit button will open Landing Page in site siteaccess.

Expected Result
Landing Page opened to edit in editor siteaccess.

Note: Accessing Page Builder via Page tab and selecting editor siteaccess will preselect this siteaccess to when Edit button is pressed on Landing Page until user logout.