Will changing /wp-login.php break s2member?

I want to change /wp-login to /login using this .htaccess edit in the article. Will it break s2member, meaning will it cause s2member not to function correctly?

(sample):
1) Redirect with .htaccess
the original .htaccess looks like that

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

edited .htaccess

RewriteBase /
RewriteRule ^login$ wp-login.php

2) Change the links from wp-logins.php to /login in functions.php w/ filter

add_filter('site_url',  'wplogin_filter', 10, 3);
function wplogin_filter( $url, $path, $orig_scheme )
{
 $old  = array( "/(wp-login.php)/");
 $new  = array( "login");
 return preg_replace( $old, $new, $url, 1);
}

———
Article – How to: change from wp-login.php to login –
http://wordpress.org/support/topic/how-to-change-from-wp-loginphp-to-login

I don’t think it’ll be a problem, but the best confirmation would be testing it.

The things I can think of related to s2Member, would be the links in the s2Member Pro login widget, or the redirection when the login fails. Also the custom profile fields in the registration form.
[hilite path]WP Admin -> Appearance -> Widgets -> s2Member Pro Login[/hilite]
[hilite path]Dashboard -› s2Member® -› General Options -› Registration/Profile Fields[/hilite]

Thanks for the response Cristián. I tested it and everything works perfectly!

Excellent! Thanks for the update. :)